pulumi · justinvp · Jun 22, 2019 · Jun 22, 2019 · Jun 22, 2019
diff --git a/.travis.yml b/.travis.yml
@@ -4,6 +4,7 @@ branches:
   only:
   - master
   - production
+  - fusion
 before_install:
 # Use travisqueue to manage build concurrency.
 - ./scripts/travisqueue.sh install

diff --git a/Makefile b/Makefile
@@ -47,8 +47,10 @@ test:
 		--exclude "/docs/reference/pkg" \
 		--exclude "/docs/reference/changelog" \
 		--exclude "https://github.com/pulumi/docs/edit/master" \
-		--exclude "https://www.linkedin.com/company/pulumi/" \
-		--exclude "https://marketplace.visualstudio.com/items?itemName=pulumi.build-and-release-task"
+		--exclude "https://www.linkedin.com/" \
+		--exclude "https://marketplace.visualstudio.com/items?itemName=pulumi.build-and-release-task" \
+		--exclude "https://blog.mapbox.com/" \
+		--exclude "https://github.com/pulls?"
 
 .PHONY: validate
 validate:
@@ -66,6 +68,9 @@ endif
 ifeq ($(TRAVIS_BRANCH),production)
 	./scripts/preview.sh production
 endif
+ifeq ($(TRAVIS_BRANCH),fusion)
+	./scripts/preview.sh fusion
+endif
 
 .PHONY: deploy
 deploy:
@@ -76,13 +81,18 @@ endif
 ifeq ($(TRAVIS_BRANCH),production)
 	./scripts/update.sh production
 endif
+ifeq ($(TRAVIS_BRANCH),fusion)
+	./scripts/update.sh fusion
+endif
 
 .PHONY: travis_push
 travis_push::
 	$(MAKE) banner
 	$(MAKE) ensure
 ifeq ($(TRAVIS_BRANCH),master)
 	HUGO_BASEURL=https://staging.pulumi.io/ $(MAKE) build
+else ifeq ($(TRAVIS_BRANCH),fusion)
+	HUGO_BASEURL=https://fusion.pulumi.io/ $(MAKE) build
 else
 	$(MAKE) build
 endif
@@ -94,6 +104,8 @@ travis_pull_request::
 	$(MAKE) ensure
 ifeq ($(TRAVIS_BRANCH),master)
 	HUGO_BASEURL=https://staging.pulumi.io/ $(MAKE) build
+else ifeq ($(TRAVIS_BRANCH),fusion)
+	HUGO_BASEURL=https://fusion.pulumi.io/ $(MAKE) build
 else
 	$(MAKE) build
 endif
@@ -106,6 +118,8 @@ travis_cron::
 	$(MAKE) ensure
 ifeq ($(TRAVIS_BRANCH),master)
 	HUGO_BASEURL=https://staging.pulumi.io/ $(MAKE) build
+else ifeq ($(TRAVIS_BRANCH),fusion)
+	HUGO_BASEURL=https://fusion.pulumi.io/ $(MAKE) build
 else
 	$(MAKE) build
 endif
@@ -116,6 +130,8 @@ travis_api::
 	$(MAKE) ensure
 ifeq ($(TRAVIS_BRANCH),master)
 	HUGO_BASEURL=https://staging.pulumi.io/ $(MAKE) build
+else ifeq ($(TRAVIS_BRANCH),fusion)
+	HUGO_BASEURL=https://fusion.pulumi.io/ $(MAKE) build
 else
 	$(MAKE) build
 endif
diff --git a/content/blog/2018-year-at-a-glance/index.md b/content/blog/2018-year-at-a-glance/index.md
@@ -16,7 +16,7 @@ Here are some of the exciting things that happened:
 
 **Launching our open source
 community.** After being hard at work for a little over a year,
-[we launched our open source project](../introducing-pulumi-a-cloud-development-platform/),
+[we launched our open source project]({{< ref "/blog/introducing-pulumi-a-cloud-development-platform" >}}),
 with the aim of making it considerably easier and more enjoyable to create and operate
 cloud software. This was a major moment for us. We had previously only shown Pulumi to a few select friends,
 family, and private beta users, and the reception was beyond our wildest expectations. We got passionate +1’s
@@ -27,11 +27,11 @@ open source contributions and passionate community leaders emerging who are help
 helping us to make Pulumi even better.
 
 **Support for major public, private, and hybrid clouds.** We launched with support for the three major public
-clouds, [AWS]({{< ref "/docs/quickstart/aws" >}}), [Azure]({{ ref "/docs/quickstart/azure" >}}), and
+clouds, [AWS]({{< ref "/docs/quickstart/aws" >}}), [Azure]({{< ref "/docs/quickstart/azure" >}}), and
 [Google Cloud]({{< ref "/docs/quickstart/gcp" >}}), and have since added capabilities across all
 of them, including adding [serverless]({{< ref "/docs/reference/tutorials/aws/tutorial-rest-api.md" >}}),
-[containers](https://github.com/pulumi/pulumi-aws-infra/blob/master/nodejs/aws-infra/examples/fargate/index.ts), and
-[infrastructure](https://github.com/pulumi/pulumi-aws-infra/blob/master/nodejs/aws-infra/examples/ec2/index.ts)
+[containers](https://github.com/pulumi/examples/blob/master/aws-ts-containers/index.ts), and
+[infrastructure](https://github.com/pulumi/examples/blob/master/aws-js-webserver/index.js)
 productivity libraries -- it is here where we believe Pulumi’s unique approach of using general purpose languages truly
 shines. We immediately had a wave of inbound interest in applying the Pulumi approach to infrastructure as code in other
 areas, and quickly added other providers including OpenStack, VMWare vSphere, Alibaba Cloud, F5 BigIP, and more. In
@@ -41,7 +41,7 @@ both of which continue to lead to significant community growth. Many customers a
 consistent engineering workflow across multi-cloud environments -- often spanning public, private, and/or hybrid clouds.
 
 **Launching our commercial SaaS product.** In October, [we launched our commercial SaaS
-product](../../../com/pulumi/blog/building-a-future-of-cloud-engineering.html), with reasonable
+product]({{< ref "/blog/building-a-future-of-cloud-engineering" >}}), with reasonable
 [pricing](https://www.pulumi.com/pricing/) so that teams of all sizes are able to get their code to the cloud
 productively, securely, and collaboratively. If Pulumi is like Git -- a local CLI and SDK -- then the Pulumi SaaS is
 like GitHub -- a hosted service to ensure you can use Pulumi in a team setting. In addition to the Team Edition, which

diff --git a/content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md b/content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md
@@ -131,5 +131,5 @@ your organization's Settings page.
 
 For annual subscriptions, we also offer invoicing that is payable with
 bank transfer or check. To discuss those options in more detail, please
-[contact us]({{ ref "/contact" }}).
+[contact us]({{< ref "/contact" >}}).
 
diff --git a/content/blog/announcing-pulumi-0.15-kubernetes-cicd-openstack-and-more/index.md b/content/blog/announcing-pulumi-0.15-kubernetes-cicd-openstack-and-more/index.md
@@ -263,7 +263,7 @@ documentation]({{< ref "/docs/reference/cd-github" >}}).
 We're excited about all the new features in this release and the new
 scenarios they enable for the Pulumi community . If you are new to
 Pulumi, [download the tools and get started
-today]({{ ref "/docs/quickstart" >}}), or [join us in
+today]({{< ref "/docs/quickstart" >}}), or [join us in
 Slack](https://slack.pulumi.io). A big thanks to all the users and
 contributors who have helped shape this release -- we can't wait to see
 what you build next !

diff --git a/content/blog/cd-made-easy-with-pulumi-and-azure-pipelines/index.md b/content/blog/cd-made-easy-with-pulumi-and-azure-pipelines/index.md
@@ -19,7 +19,7 @@ infrastructure is just a few steps away for you and your teams.
 To make it easy to use Pulumi with Azure, we are announcing an
 open-source task extension for Azure Pipelines! The task extension will
 manage the installation of the Pulumi CLI, and run the [Pulumi
-commands]({{ ref "/docs/reference/commands" >}}) you specify against
+commands]({{< ref "/docs/reference/commands" >}}) you specify against
 your stack.
 
 You can install the task extension directly from the [Visual Studio

diff --git a/...t/blog/code-deploy-and-manage-a-serverless-rest-api-on-aws-with-pulumi/index.md b/...t/blog/code-deploy-and-manage-a-serverless-rest-api-on-aws-with-pulumi/index.md
@@ -186,7 +186,7 @@ To clean up the resources, run `pulumi destroy`.
 ## Next steps
 
 The
-[sample code for this application](https://github.com/pulumi/examples/tree/master/cloud-js-httpendpoint)
+[sample code for this application](https://github.com/pulumi/examples/tree/master/cloud-js-httpserver)
 is available in the Pulumi examples repo on GitHub. For an end-to-end
 TypeScript application with a frontend, see the
 [URL shortener sample](https://github.com/pulumi/examples/tree/master/cloud-ts-url-shortener).
diff --git a/...umi-azure-open-source-sdks/intialized.png → ...mi-azure-open-source-sdks/initialized.png b/...umi-azure-open-source-sdks/intialized.png → ...mi-azure-open-source-sdks/initialized.png
diff --git a/...a-science-on-demand-spinning-up-a-wallaroo-cluster-is-easy-with-pulumi/index.md b/...a-science-on-demand-spinning-up-a-wallaroo-cluster-is-easy-with-pulumi/index.md
@@ -260,7 +260,7 @@ While the work is being performed, we can take a look at the metrics URL
 printed out on the screen to find out how the work is being distributed.
 
 > To see the cluster's real-time metrics, please visit
-> http://ec2-54-200-198-6.us-west-2.compute.amazonaws.com:4000
+> `http://ec2-54-200-198-6.us-west-2.compute.amazonaws.com:4000`
 
 ![wallaroo-2](./wallaroo-2.png)
 

diff --git a/content/blog/how-we-use-pulumi-to-build-pulumi/index.md b/content/blog/how-we-use-pulumi-to-build-pulumi/index.md
@@ -26,7 +26,7 @@ We use Pulumi for raw infrastructure provisioning, defining the core
 networking layer for our AWS-based backend infrastructure. And we use
 Pulumi to define how our application services are deployed into ECS
 using just a few lines of code. Pulumi hosts and manages static content
-for [www.pulumi.com](http://www.pulumi.com/) and [get.pulumi.com](../../../com/pulumi/blog/index.html).
+for [www.pulumi.com](https://www.pulumi.com/) and [get.pulumi.com](https://get.pulumi.com).
 We use Pulumi to
 define the CloudWatch dashboards connected to our infrastructure. And
 for monitoring, Pulumi defines metrics and notifications/alarms in

diff --git a/content/blog/improving-kubernetes-management-with-pulumis-await-logic/index.md b/content/blog/improving-kubernetes-management-with-pulumis-await-logic/index.md
@@ -61,7 +61,7 @@ applications, or sharing responsibilities between teams.
 
 
 2) Reliably integrate with
-[**CI/CD systems**]({{ ref "/docs/reference/cd" >}}) for infrastructure and
+[**CI/CD systems**]({{< ref "/docs/reference/cd" >}}) for infrastructure and
 application deployments without requiring hardcoded timeouts, or
 scripting kubectl and parsing the resulting JSON/YAML to detect errors.
 If errors are encountered, Pulumi automatically surfaces the relevant

diff --git a/content/blog/lambdas-as-lambdas-the-magic-of-simple-serverless-functions/index.md b/content/blog/lambdas-as-lambdas-the-magic-of-simple-serverless-functions/index.md
@@ -164,7 +164,7 @@ great compiler work underpinning them.
 So let's dig in -- how does this all really work?
 
 (Note that, if you want some of the more nitty gritty details, we have a
-[doc](https://github.com/pulumi/docs/blob/master/reference/serializing-functions.md)
+[doc]({{< relref "/docs/reference/serializing-functions.md" >}})
 going in depth. For now, we'll try to stick to providing a high-level
 overview of what's going on, so that we can grok the basic approach.)
 

diff --git a/content/blog/managing-github-webhooks-with-pulumi/index.md b/content/blog/managing-github-webhooks-with-pulumi/index.md
@@ -84,7 +84,7 @@ webhook and fill in my information:
 
 - Payload URL: The value of the `url` output of my Pulumi program (in
   this case it is
-  <https://t1vyz1x203.execute-api.us-west-1.amazonaws.com/stage/>).
+  `https://t1vyz1x203.execute-api.us-west-1.amazonaws.com/stage/`).
 - Content Type: `application-json`. I know we'll be inspecting this
   content as we develop the hook and since we're writing the
   implementation in TypeScript, it will be easier to interact with

diff --git a/content/blog/mapbox-iot-as-code-with-pulumi-crosswalk-for-aws/index.md b/content/blog/mapbox-iot-as-code-with-pulumi-crosswalk-for-aws/index.md
@@ -58,8 +58,8 @@ not remember what you deployed as your cloud environments scale:
 
 Lets now work through the solution flow with some sample snippets of
 code. To get access to the complete piece of code, please connect with
-Mapbox solution team [here](chris.toomey@mapbox.com) and
-Pulumi team [here](sales@pulumi.com). We will be happy to help you sample test this
+Mapbox solution team [here](mailto:chris.toomey@mapbox.com) and
+Pulumi team [here](mailto:sales@pulumi.com). We will be happy to help you sample test this
 solution on AWS!
 
 **STEP 1: Create a Pulumi project using an AWS JavaScript template**
@@ -144,8 +144,8 @@ used by Mapbox streamprocessor and Firehose all created with Pulumi AWS
 and AWSX libraries.
 
 To get this piece of code, please connect with Mapbox solution team
-[here](chris.toomey@mapbox.com) and Pulumi team
-[here](sales@pulumi.com).
+[here](mailto:chris.toomey@mapbox.com) and Pulumi team
+[here](mailto:sales@pulumi.com).
 
 **STEP 3: Create a consumption API for the map client to consume from a
 data source**
@@ -157,8 +157,8 @@ query this data out of DynamoDB. The sample code in `index.js` will look
 like this:
 
 To get this piece of code, please connect with Mapbox solution team
-[here](chris.toomey@mapbox.com) and Pulumi team
-[here](sales@pulumi.com).
+[here](mailto:chris.toomey@mapbox.com) and Pulumi team
+[here](mailto:sales@pulumi.com).
 
     //* Create DynamoDB Table
     const assetTable = new aws.dynamodb.Table("assetTable", {

diff --git a/content/blog/program-kubernetes-with-11-cloud-native-pulumi-pearls/index.md b/content/blog/program-kubernetes-with-11-cloud-native-pulumi-pearls/index.md
@@ -495,8 +495,6 @@ Kubernetes cluster for everybody!
 
 ## 8. Build and Deploy Container Images Alongside Configuration Updates
 
-[ [Code](https://github.com/pulumi/pulumi-docker/tree/master/docker/tests/image) ]
-
 One scenario we often encounter in practice is the need to coordinate
 Docker registry provisioning and management (using one set of tools),
 with building and pushing new Docker images (using another set of
@@ -563,7 +561,7 @@ pipeline is too. In fact, each Pulumi program really is a deployment
 workflow expressed in code. The Pulumi CLI is responsible for evaluating
 programs, producing goal states, diffing states to produce plans, and
 carrying them out. The Pulumi hosted service at
-<app.pulumi.com> is used for robust concurrency
+[https://app.pulumi.com](https://app.pulumi.com) is used for robust concurrency
 and state management so that deployments can be done continuously in a
 team environment, with perfect auditability of who changed what and
 when, and so that deployments are repeatable and failures recoverable.

diff --git a/content/blog/pulumi-and-docker-development-to-production/index.md b/content/blog/pulumi-and-docker-development-to-production/index.md
@@ -173,7 +173,7 @@ tools we already use for software engineering:
 
 1. Abstraction, encapsulation, and code reuse for infrastructure and
    applications
-2. [Testing](../../../com/pulumi/blog/testing-your-infrastructure-as-code-with-pulumi.html),
+2. [Testing]({{< ref "/blog/testing-your-infrastructure-as-code-with-pulumi" >}}),
    both unit and integration
 3. IDEs and tools for detecting errors extremely early in a developer's
    inner loop, instead of at deployment time

diff --git a/content/blog/pulumi-heart-google-cloud-platform/index.md b/content/blog/pulumi-heart-google-cloud-platform/index.md
@@ -88,7 +88,7 @@ will it proceed (with a full audit history):
     ...
 
 Learn more about working with Pulumi and Google Cloud infrastructure in
-this [GCE Web Server]({{ ref "/docs/reference/tutorials/gcp/tutorial-gce-webserver" >}})
+this [GCE Web Server]({{< ref "/docs/reference/tutorials/gcp/tutorial-gce-webserver" >}})
 tutorial.
 
 ## Working with Kubernetes and Google Container Engine (GKE)

diff --git a/content/blog/simple-reproducible-kubernetes-deployments/index.md b/content/blog/simple-reproducible-kubernetes-deployments/index.md
@@ -99,7 +99,7 @@ ecosystem.
 
 > Note: It is also possible to directly deploy existing Kubernetes YAML
 > objects, as a stepping stone. See the example
-> [here](https://github.com/pulumi/pulumi-kubernetes/blob/master/examples/yaml-guestbook/index.ts).
+> [here](https://github.com/pulumi/pulumi-kubernetes/blob/master/tests/examples/yaml-guestbook/index.ts).
 > This lets you reap all of the benefits of the deployment workflow
 > called out in this post without needing to rewrite all of your
 > Kubernetes YAML. It's easy to then rewrite it piecemeal, one step at a

diff --git a/content/blog/using-pulumi-with-aws-sqs-and-lambdas/index.md b/content/blog/using-pulumi-with-aws-sqs-and-lambdas/index.md
@@ -138,7 +138,7 @@ changes in the upcoming releases for both projects!
 
 After getting the change in we went back and tested our example and saw
 that now everything worked as expected. We also expanded things out
-[in an example](https://github.com/pulumi/pulumi-aws-serverless/blob/master/nodejs/aws-serverless/examples/queue/index.ts)
+[in an example](https://github.com/pulumi/pulumi-aws/blob/master/examples/queue/index.ts)
 to show how you might use this in practice. In this example, we receive
 the event, and then just write the data of it into an [S3 Bucket](https://aws.amazon.com/s3/). Running this example we now
 successfully see:

diff --git a/content/docs/reference/cli/pulumi.md b/content/docs/reference/cli/pulumi.md
@@ -45,21 +45,21 @@ For more information, please visit the project page: https://pulumi.io
 
 ### SEE ALSO
 
-* [pulumi cancel](/reference/cli/pulumi_cancel/)	 - Cancel a stack's currently running update, if any
-* [pulumi config](/reference/cli/pulumi_config/)	 - Manage configuration
-* [pulumi destroy](/reference/cli/pulumi_destroy/)	 - Destroy an existing stack and its resources
-* [pulumi history](/reference/cli/pulumi_history/)	 - Update history for a stack
-* [pulumi login](/reference/cli/pulumi_login/)	 - Log into the Pulumi service
-* [pulumi logout](/reference/cli/pulumi_logout/)	 - Log out of the Pulumi service
-* [pulumi logs](/reference/cli/pulumi_logs/)	 - Show aggregated logs for a stack
-* [pulumi new](/reference/cli/pulumi_new/)	 - Create a new Pulumi project
-* [pulumi plugin](/reference/cli/pulumi_plugin/)	 - Manage language and resource provider plugins
-* [pulumi preview](/reference/cli/pulumi_preview/)	 - Show a preview of updates to a stack's resources
-* [pulumi refresh](/reference/cli/pulumi_refresh/)	 - Refresh the resources in a stack
-* [pulumi stack](/reference/cli/pulumi_stack/)	 - Manage stacks
-* [pulumi state](/reference/cli/pulumi_state/)	 - Edit the current stack's state
-* [pulumi up](/reference/cli/pulumi_up/)	 - Create or update the resources in a stack
-* [pulumi version](/reference/cli/pulumi_version/)	 - Print Pulumi's version number
-* [pulumi whoami](/reference/cli/pulumi_whoami/)	 - Display the current logged-in user
+* [pulumi cancel](/docs/reference/cli/pulumi_cancel/)	 - Cancel a stack's currently running update, if any
+* [pulumi config](/docs/reference/cli/pulumi_config/)	 - Manage configuration
+* [pulumi destroy](/docs/reference/cli/pulumi_destroy/)	 - Destroy an existing stack and its resources
+* [pulumi history](/docs/reference/cli/pulumi_history/)	 - Update history for a stack
+* [pulumi login](/docs/reference/cli/pulumi_login/)	 - Log into the Pulumi service
+* [pulumi logout](/docs/reference/cli/pulumi_logout/)	 - Log out of the Pulumi service
+* [pulumi logs](/docs/reference/cli/pulumi_logs/)	 - Show aggregated logs for a stack
+* [pulumi new](/docs/reference/cli/pulumi_new/)	 - Create a new Pulumi project
+* [pulumi plugin](/docs/reference/cli/pulumi_plugin/)	 - Manage language and resource provider plugins
+* [pulumi preview](/docs/reference/cli/pulumi_preview/)	 - Show a preview of updates to a stack's resources
+* [pulumi refresh](/docs/reference/cli/pulumi_refresh/)	 - Refresh the resources in a stack
+* [pulumi stack](/docs/reference/cli/pulumi_stack/)	 - Manage stacks
+* [pulumi state](/docs/reference/cli/pulumi_state/)	 - Edit the current stack's state
+* [pulumi up](/docs/reference/cli/pulumi_up/)	 - Create or update the resources in a stack
+* [pulumi version](/docs/reference/cli/pulumi_version/)	 - Print Pulumi's version number
+* [pulumi whoami](/docs/reference/cli/pulumi_whoami/)	 - Display the current logged-in user
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_cancel.md b/content/docs/reference/cli/pulumi_cancel.md
@@ -48,6 +48,6 @@ pulumi cancel [<stack-name>] [flags]
 
 ### SEE ALSO
 
-* [pulumi](/reference/cli/pulumi/)	 - Pulumi command line
+* [pulumi](/docs/reference/cli/pulumi/)	 - Pulumi command line
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_config.md b/content/docs/reference/cli/pulumi_config.md
@@ -45,10 +45,10 @@ pulumi config [flags]
 
 ### SEE ALSO
 
-* [pulumi](/reference/cli/pulumi/)	 - Pulumi command line
-* [pulumi config get](/reference/cli/pulumi_config_get/)	 - Get a single configuration value
-* [pulumi config refresh](/reference/cli/pulumi_config_refresh/)	 - Update the local configuration based on the most recent deployment of the stack
-* [pulumi config rm](/reference/cli/pulumi_config_rm/)	 - Remove configuration value
-* [pulumi config set](/reference/cli/pulumi_config_set/)	 - Set configuration value
+* [pulumi](/docs/reference/cli/pulumi/)	 - Pulumi command line
+* [pulumi config get](/docs/reference/cli/pulumi_config_get/)	 - Get a single configuration value
+* [pulumi config refresh](/docs/reference/cli/pulumi_config_refresh/)	 - Update the local configuration based on the most recent deployment of the stack
+* [pulumi config rm](/docs/reference/cli/pulumi_config_rm/)	 - Remove configuration value
+* [pulumi config set](/docs/reference/cli/pulumi_config_set/)	 - Set configuration value
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_config_get.md b/content/docs/reference/cli/pulumi_config_get.md
@@ -42,6 +42,6 @@ pulumi config get <key> [flags]
 
 ### SEE ALSO
 
-* [pulumi config](/reference/cli/pulumi_config/)	 - Manage configuration
+* [pulumi config](/docs/reference/cli/pulumi_config/)	 - Manage configuration
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_config_refresh.md b/content/docs/reference/cli/pulumi_config_refresh.md
@@ -42,6 +42,6 @@ pulumi config refresh [flags]
 
 ### SEE ALSO
 
-* [pulumi config](/reference/cli/pulumi_config/)	 - Manage configuration
+* [pulumi config](/docs/reference/cli/pulumi_config/)	 - Manage configuration
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_config_rm.md b/content/docs/reference/cli/pulumi_config_rm.md
@@ -41,6 +41,6 @@ pulumi config rm <key> [flags]
 
 ### SEE ALSO
 
-* [pulumi config](/reference/cli/pulumi_config/)	 - Manage configuration
+* [pulumi config](/docs/reference/cli/pulumi_config/)	 - Manage configuration
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_config_set.md b/content/docs/reference/cli/pulumi_config_set.md
@@ -45,6 +45,6 @@ pulumi config set <key> [value] [flags]
 
 ### SEE ALSO
 
-* [pulumi config](/reference/cli/pulumi_config/)	 - Manage configuration
+* [pulumi config](/docs/reference/cli/pulumi_config/)	 - Manage configuration
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_destroy.md b/content/docs/reference/cli/pulumi_destroy.md
@@ -59,6 +59,6 @@ pulumi destroy [flags]
 
 ### SEE ALSO
 
-* [pulumi](/reference/cli/pulumi/)	 - Pulumi command line
+* [pulumi](/docs/reference/cli/pulumi/)	 - Pulumi command line
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_history.md b/content/docs/reference/cli/pulumi_history.md
@@ -44,6 +44,6 @@ pulumi history [flags]
 
 ### SEE ALSO
 
-* [pulumi](/reference/cli/pulumi/)	 - Pulumi command line
+* [pulumi](/docs/reference/cli/pulumi/)	 - Pulumi command line
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019
diff --git a/content/docs/reference/cli/pulumi_login.md b/content/docs/reference/cli/pulumi_login.md
@@ -69,6 +69,6 @@ pulumi login [<url>] [flags]
 
 ### SEE ALSO
 
-* [pulumi](/reference/cli/pulumi/)	 - Pulumi command line
+* [pulumi](/docs/reference/cli/pulumi/)	 - Pulumi command line
 
 ###### Auto generated by spf13/cobra on 7-Jun-2019