Fix broken links on docs pages

config/_default/config.yml

@@ -1,7 +1,7 @@
 languageCode: en-us
 title: Pulumi - Infrastructure as Code in Any Programming Language
 
-refLinksErrorLevel: WARNING
+refLinksErrorLevel: ERROR
 security:
  funcs:
  getenv:

content/blog/2019-year-at-a-glance/index.md

@@ -23,9 +23,9 @@ It's impossible to highlight everything, but here are some of our favorite miles
 
 **Pulumi Crosswalk.** We introduced the Pulumi Crosswalk brand for our collection of cloud-specific higher level frameworks that simplify many common infrastructure patterns, while also including built-in best practices. Throughout the year, we've rounded out that support, starting with AWS, then Kubernetes, as well as some initial steps towards frameworks for Azure and Google Cloud:
 
-* **[Pulumi Crosswalk for AWS](/blog/introducing-pulumi-crosswalk-for-aws-the-easiest-way-to-aws/)** simplifies common AWS patterns, including [creating VPCs](/docs/clouds/aws/guides/vpc/), [ECS, EKS, and Fargate clusters](/blog/running-containers-in-aws-the-lowdown-ecs-fargate-and-eks/), [building and publishing Docker images to ECR registries](/blog/building-and-publishing-docker-images-to-a-private-amazon-ecr-repository/), and [more](/docs/clouds/aws/guides/).
+* **[Pulumi Crosswalk for AWS](/blog/introducing-pulumi-crosswalk-for-aws-the-easiest-way-to-aws/)** simplifies common AWS patterns, including [creating VPCs](/docs/iac/clouds/aws/guides/vpc/), [ECS, EKS, and Fargate clusters](/blog/running-containers-in-aws-the-lowdown-ecs-fargate-and-eks/), [building and publishing Docker images to ECR registries](/blog/building-and-publishing-docker-images-to-a-private-amazon-ecr-repository/), and [more](/docs/iac/clouds/aws/guides/).
 
-* **[Pulumi Crosswalk for Kubernetes](/blog/crosswalk-kubernetes/)** encapsulates battle-tested approaches to running Kubernetes clusters and related infrastructure in production. This includes [playbooks for running Kubernetes in AWS, Azure, or Google Cloud](/docs/clouds/kubernetes/guides/playbooks/), as well as [kx](/blog/introducing-kx/), a highly productive library that eliminates the "walls of YAML" boilerplate from your Kubernetes applications configurations.
+* **[Pulumi Crosswalk for Kubernetes](/blog/crosswalk-kubernetes/)** encapsulates battle-tested approaches to running Kubernetes clusters and related infrastructure in production. This includes [playbooks for running Kubernetes in AWS, Azure, or Google Cloud](/docs/iac/clouds/kubernetes/guides/playbooks/), as well as [kx](/blog/introducing-kx/), a highly productive library that eliminates the "walls of YAML" boilerplate from your Kubernetes applications configurations.
 
 * Although still works in progress, Pulumi Crosswalk for Azure will include [simple Azure Functions callbacks](/blog/serverless-as-simple-callbacks-with-pulumi-and-azure-functions/) and [globally distributed applications that auto-scale alongside Cosmos DB](/blog/how-to-build-globally-distributed-applications-with-azure-cosmos-db-and-pulumi/), and Pulumi Crosswalk for Google Cloud will include [simplified Google Functions](/blog/simple-serverless-programming-with-google-cloud-functions-and-pulumi/).
 
@@ -37,9 +37,9 @@ It's impossible to highlight everything, but here are some of our favorite miles
 
 **[Enhanced, pluggable secrets](/blog/managing-secrets-with-pulumi/).** We heard that keeping secrets from leaking in plaintext to your start files is a challenge with current infrastructure as code tools. So, we deepend the way secrets integrate with Pulumi's engine, including transitive encryption so that, no matter where your secret goes in your program, it won't leak in plaintext. In addition, we added the ability to [use your own secrets provider for encryption](/docs/concepts/secrets#configuring-secrets-encryption), including AWS KMS, Azure KeyVault, Google Cloud KMS, and HashiCorp Vault. This ensures you get great ease-of-use — falling into the "pit of success" with secrets — while still leveraging your existing organization's approach.
 
-**More state storage options.** Although the hosted Pulumi SaaS works great for most end users, offering the right mix of convenience and control, we understand it doesn't work for everyone. It is now possible to store state locally using the `pulumi login --local` command, or to [configure Pulumi to store state in AWS S3, Azure Blob Storage, or Google Cloud Storage](/docs/concepts/state#using-a-self-managed-backend). Additionally, [Pulumi Enterprise offers a self-hosted option](/docs/pulumi-cloud/self-hosted/), so that you can still benefit from the Pulumi SaaS's features around identity, policies, and controls, while hosting it in your own cloud account or behind your firewall.
+**More state storage options.** Although the hosted Pulumi SaaS works great for most end users, offering the right mix of convenience and control, we understand it doesn't work for everyone. It is now possible to store state locally using the `pulumi login --local` command, or to [configure Pulumi to store state in AWS S3, Azure Blob Storage, or Google Cloud Storage](/docs/iac/concepts/state-and-backends#using-a-self-managed-backend). Additionally, [Pulumi Enterprise offers a self-hosted option](/docs/pulumi-cloud/self-hosted/), so that you can still benefit from the Pulumi SaaS's features around identity, policies, and controls, while hosting it in your own cloud account or behind your firewall.
 
-**[More CI/CD integrations](/docs/using-pulumi/continuous-delivery/).** In partnership with customers, and in some cases the CI/CD vendors themselves, we have continued adding more CI/CD integrations, to enable automated delivery of your infrastructure. This includes [Jenkins](/docs/using-pulumi/continuous-delivery/jenkins/), [Azure DevOps Pipelines](/blog/cd-made-easy-with-pulumi-and-azure-pipelines/), [Octopus Deploy](/docs/using-pulumi/continuous-delivery/octopus-deploy/), [Codefresh](/docs/using-pulumi/continuous-delivery/codefresh/), and [revised support for GitHub Actions](/docs/using-pulumi/continuous-delivery/github-actions/).
+**[More CI/CD integrations](/docs/iac/packages-and-automation/continuous-delivery/).** In partnership with customers, and in some cases the CI/CD vendors themselves, we have continued adding more CI/CD integrations, to enable automated delivery of your infrastructure. This includes [Jenkins](/docs/iac/packages-and-automation/continuous-delivery/jenkins/), [Azure DevOps Pipelines](/blog/cd-made-easy-with-pulumi-and-azure-pipelines/), [Octopus Deploy](/docs/iac/packages-and-automation/continuous-delivery/octopus-deploy/), [Codefresh](/docs/iac/packages-and-automation/continuous-delivery/codefresh/), and [revised support for GitHub Actions](/docs/iac/packages-and-automation/continuous-delivery/github-actions/).
 
 **Coexistence and conversion tools.** We know that many teams have existing infrastructure in place. We want to make it a easy as possible to choose Pulumi and, as we've worked with major customers to transition away from existing infrastructure tools, we've built tools to help ease the adoption process. This includes the following approaches:
 

content/blog/adopting-existing-cloud-resources-into-pulumi/index.md

@@ -8,7 +8,7 @@ tags: ["migration"]
 ---
 
 {{% notes %}}
-See [Migrating From Terraform to Pulumi](/docs/using-pulumi/adopting-pulumi/migrating-to-pulumi/from-terraform/) for updated documentation on migrating from Terraform.
+See [Migrating From Terraform to Pulumi](/docs/iac/adopting-pulumi/migrating-to-pulumi/from-terraform/) for updated documentation on migrating from Terraform.
 {{% /notes %}}
 
 Most cloud infrastructure projects involve working with existing cloud resources — either building on top of existing resources or adopting existing resources under management with a new and more robust infrastructure provisioning solution.

content/blog/amazing-performance/index.md

@@ -75,7 +75,7 @@ In both scenarios, importing TypeScript when it's not used results in a 300ms sl
 
 ### Timely Lease Renewal
 
-Another quick win involved the renewal of a new lease, which resulted in another 120ms shaved off of boot time. When the Pulumi CLI kicks off a preview, projects that use the [Service backend](/docs/concepts/state/#pulumi-service-backend) are authenticated with the Service so the CLI can fetch the current state. During authentication, the CLI exchanges user credentials for a short-lived access token. This access token is valid for a fixed amount of time, called a lease, after which they expire. The CLI can renew a lease by making another request to the Service to extend the duration for which the lease is valid.
+Another quick win involved the renewal of a new lease, which resulted in another 120ms shaved off of boot time. When the Pulumi CLI kicks off a preview, projects that use the [Service backend](/docs/iac/concepts/state-and-backends/#pulumi-service-backend) are authenticated with the Service so the CLI can fetch the current state. During authentication, the CLI exchanges user credentials for a short-lived access token. This access token is valid for a fixed amount of time, called a lease, after which they expire. The CLI can renew a lease by making another request to the Service to extend the duration for which the lease is valid.
 
 We noticed that the first time the CLI renewed the lease, it blocked further execution until the renewal was complete, introducing an unnecessary slowdown of 120ms. [The fix](https://github.com/pulumi/pulumi/pull/10462) was to remove this renewal from the critical path by running it in the backend. By starting the HTTP call on a background thread and only blocking if the token is needed but not renewed, we've eliminated the 120ms slowdown.
 

content/blog/amazon-eks-anywhere-bare-metal/index.md

@@ -68,7 +68,7 @@ const page = new eksa.metal.Cluster("cluster", {
 
 To use the component, take the following steps:
 
-1. Make sure you’ve followed the steps to [setup Pulumi and AWS](/docs/clouds/aws/get-started/)
+1. Make sure you’ve followed the steps to [setup Pulumi and AWS](/docs/iac/get-started/aws/)
 
 1. Grab the EKS-A component and example code on [Pulumiverse](https://github.com/pulumiverse/pulumi-aws-eksa).
 

content/blog/announcing-pulumi-0.15-kubernetes-cicd-openstack-and-more/index.md

@@ -23,7 +23,7 @@ TypeScript support), richer
 (serverless frameworks for Azure and
 Google Cloud),  and is more deeply
 integrated into the application lifecycle
-([GitHub App for CI/CD integration](/docs/using-pulumi/continuous-delivery/github-app)).
+([GitHub App for CI/CD integration](/docs/iac/packages-and-automation/continuous-delivery/github-app)).
 
 In this post, we'll take a quick tour of these new features. Stay tuned
 for follow up blog posts to dive deeper into individual topics.
@@ -241,7 +241,7 @@ export let url = f.function.httpsTriggerUrl;
 
 ## GitHub App for CI/CD Integration
 
-Pulumi already works with [your favorite CI/CD systems](/docs/using-pulumi/continuous-delivery/)
+Pulumi already works with [your favorite CI/CD systems](/docs/iac/packages-and-automation/continuous-delivery/)
 to accomplish automated
 and continuous deployments of cloud infrastructure and applications.
 This is how Pulumi deploys and manages our own infrastructure that runs
@@ -262,7 +262,7 @@ infrastructure changes.
 
 The Pulumi GitHub App is still in preview as we work to support more CI
 systems and extend its capabilities. For information on how to install
-it and configure it with your CI system, please [read the documentation](/docs/using-pulumi/continuous-delivery/github-app/).
+it and configure it with your CI system, please [read the documentation](/docs/iac/packages-and-automation/continuous-delivery/github-app/).
 
 ## Summary
 

content/blog/any-terraform-provider/index.md

@@ -43,7 +43,7 @@ This is enabled by our new Local Packages feature, which lets you generate Pulum
 
  {{< video title="Using Planetscale with Pulumi" src="anytfplanetscale.mp4" autoplay="true" loop="true" >}}
 
-Local packages are available as a convenient alternative to the existing support for authoring Native or Bridged Pulumi Packages. You can read more about all of the options available to authoring and using Pulumi Packages in the [Pulumi Packages documentation](https://www.pulumi.com/docs/using-pulumi/pulumi-packages/), or about how to generate a local package for a Terraform or OpenTofu provider in the [Any Terraform Provider](https://www.pulumi.com/registry/packages/terraform-provider/) docs.
+Local packages are available as a convenient alternative to the existing support for authoring Native or Bridged Pulumi Packages. You can read more about all of the options available to authoring and using Pulumi Packages in the [Pulumi Packages documentation](https://www.pulumi.com/docs/iac/packages-and-automation/pulumi-packages/debugging-provider-packages/), or about how to generate a local package for a Terraform or OpenTofu provider in the [Any Terraform Provider](https://www.pulumi.com/registry/packages/terraform-provider/) docs.
 
 ## Walkthrough
 
@@ -172,4 +172,4 @@ Take the new support for using any Terraform or OpenTofu provider from Pulumi fo
 
 * [Getting Started](https://www.pulumi.com/registry/packages/terraform-provider/)
 * [Installation and Configuration](https://www.pulumi.com/registry/packages/terraform-provider/installation-configuration/)
-* [Overview of Pulumi Packages](https://www.pulumi.com/docs/using-pulumi/pulumi-packages/)
+* [Overview of Pulumi Packages](https://www.pulumi.com/docs/iac/packages-and-automation/pulumi-packages/debugging-provider-packages/)

content/blog/api-gateway-to-eventbridge/index.md

@@ -21,7 +21,7 @@ tags:
  - serverless
 ---
 
-If you're familiar with [Amazon API Gateway](https://aws.amazon.com/api-gateway/), you know it's all about making it easier to provision and manage a web API. Maybe you've used it, as I have, with [Crosswalk](/docs/clouds/aws/guides/), our AWS extension library, to stand up a REST API and handle requests with AWS Lambda functions:
+If you're familiar with [Amazon API Gateway](https://aws.amazon.com/api-gateway/), you know it's all about making it easier to provision and manage a web API. Maybe you've used it, as I have, with [Crosswalk](/docs/iac/clouds/aws/guides/), our AWS extension library, to stand up a REST API and handle requests with AWS Lambda functions:
 
 ```typescript
 import * as awsx from "@pulumi/awsx";

content/blog/architect-aws-application-infra-with-pulumi-stack-references/index.md

@@ -453,4 +453,4 @@ information between these projects. You can find a runable version of this infra
 This demonstrates the suggested way of architecting Pulumi applications both for operability and collaboration.
 
 You can try this code today get started with Pulumi today at [https://www.pulumi.com](/) and
-following the [Getting Started](/docs/clouds/aws/get-started/) for managing AWS resources with Pulumi.
+following the [Getting Started](/docs/iac/get-started/aws/) for managing AWS resources with Pulumi.

content/blog/automatically-enforcing-aws-resource-tagging-policies/index.md

@@ -739,7 +739,7 @@ In this post, we've seen some ways to enforce AWS tagging best practices. This i
 
 Check out these resources to get started with Pulumi's open source platform:
 
-* [AWS getting started guide](/docs/clouds/aws/get-started/)
+* [AWS getting started guide](/docs/iac/get-started/aws/)
 * [Policy as Code getting started guide](/docs/using-pulumi/crossguard/get-started/)
 * [Full example code used in this post](https://github.com/joeduffy/aws-tags-example)