Fix all links after replacing master with v2.0-preview

A lot of our content dirs had links to master when they shouldn't have.
These are now replaced with local links.

Signed-off-by: Nic Cope <[email protected]>

Author: negz

content/master/_index.md

@@ -12,7 +12,7 @@ for platform engineering.
 
 Crossplane organizes its documentation into the following sections:
 
-* [What's Crossplane?]({{<ref "whats-crossplane">}}) introduces Crossplane
+* [What's Crossplane?]({{<ref "./whats-crossplane">}}) introduces Crossplane
   and explains why you should use it.
 
 * [What's New in v2?]({{<ref "whats-new">}}) highlights what's changed in

content/master/whats-new/_index.md

@@ -47,7 +47,7 @@ Read about Crossplane v2's [backward compatibility](#backward-compatibility).
 
 {{<hint "note">}}
 This page assumes you're familiar with Crossplane. New to Crossplane? Read
-[What's Crossplane]({{<ref "whats-crossplane">}}) instead.
+[What's Crossplane]({{<ref "../whats-crossplane">}}) instead.
 {{</hint>}}
 
 

content/v1.18/concepts/composition-revisions.md

@@ -449,7 +449,7 @@ vpc-staging   True     myvpcs.aws.example.upbound.io-727b3c8   Automatic   map[c
 {{< /hint >}}
 
 
-[composition type]: {{<ref "../../master/concepts/compositions" >}}
-[Compositions]: {{<ref "../../master/concepts/compositions" >}}
+[composition type]: {{<ref "../concepts/compositions" >}}
+[Compositions]: {{<ref "../concepts/compositions" >}}
 [canary]: https://martinfowler.com/bliki/CanaryRelease.html
-[install guide]: {{<ref "../../master/software/install" >}}
+[install guide]: {{<ref "../software/install" >}}

content/v1.18/concepts/connection-details.md

@@ -5,14 +5,14 @@ description: "How to create and manage connection details across Crossplane mana
 ---
 
 Using connection details in Crossplane requires the following components:
-* Defining the `writeConnectionSecretToRef.name` in a [Claim]({{<ref "/master/concepts/claims#claim-connection-secrets">}}).
-* Defining the `writeConnectionSecretsToNamespace` value in the [Composition]({{<ref "/master/concepts/compositions#composite-resource-combined-secret">}}).
+* Defining the `writeConnectionSecretToRef.name` in a [Claim]({{<ref "../concepts/claims#claim-connection-secrets">}}).
+* Defining the `writeConnectionSecretsToNamespace` value in the [Composition]({{<ref "../concepts/compositions#composite-resource-combined-secret">}}).
 * Define the `writeConnectionSecretToRef` name and namespace for each resource in the
-  [Composition]({{<ref "/master/concepts/compositions#composed-resource-secrets">}}).
+  [Composition]({{<ref "../concepts/compositions#composed-resource-secrets">}}).
 * Define the list of secret keys produced by each composed resource with in the
-  [Composition]({{<ref "/master/concepts/compositions">}}).
+  [Composition]({{<ref "../concepts/compositions">}}).
 * Optionally, define the `connectionSecretKeys` in a 
-  [CompositeResourceDefinition]({{<ref "/master/concepts/composite-resource-definitions#manage-connection-secrets">}}).
+  [CompositeResourceDefinition]({{<ref "../concepts/composite-resource-definitions#manage-connection-secrets">}}).
 
 {{<hint "note">}}
 This guide discusses creating Kubernetes secrets.  
@@ -23,7 +23,7 @@ with an external secret store.
 {{</hint >}}
 
 ## Background
-When a [Provider]({{<ref "/master/concepts/providers">}}) creates a managed
+When a [Provider]({{<ref "../concepts/providers">}}) creates a managed
 resource, the resource may generate resource-specific details. These details can include 
 usernames, passwords or connection details like an IP address.  
 
@@ -37,10 +37,10 @@ detail_ from a managed resource.
 <!-- vale gitlab.SentenceLength = NO -->
 <!-- wordy because of type names -->
 When a managed resource is part of a 
-[Composition]({{<ref "/master/concepts/compositions">}}), the Composition, 
-[Composite Resource Definition]({{<ref "/master/concepts/composite-resource-definitions">}}) 
+[Composition]({{<ref "../concepts/compositions">}}), the Composition, 
+[Composite Resource Definition]({{<ref "../concepts/composite-resource-definitions">}}) 
 and optionally, the 
-[Claim]({{<ref "/master/concepts/claims">}}) define what details are visible
+[Claim]({{<ref "../concepts/claims">}}) define what details are visible
 and where they're stored. 
 <!-- vale gitlab.SentenceLength = YES -->
 
@@ -213,17 +213,17 @@ spec:
 <!-- under 25 words -->
 When a managed resource creates connection secrets, Crossplane can write the 
 secrets to a 
-[Kubernetes secret]({{<ref "/master/concepts/managed-resources#publish-secrets-to-kubernetes">}})
+[Kubernetes secret]({{<ref "../concepts/managed-resources#publish-secrets-to-kubernetes">}})
 or an 
-[external secret store]({{<ref "/master/concepts/managed-resources#publish-secrets-to-an-external-secrets-store">}}).
+[external secret store]({{<ref "../concepts/managed-resources#publish-secrets-to-an-external-secrets-store">}}).
 <!-- vale gitlab.SentenceLength = YES -->
 <!-- vale gitlab.Substitutions = YES -->
 
 Creating an individual managed resource shows the connection secrets the
 resource creates. 
 
 {{<hint "note" >}}
-Read the [managed resources]({{<ref "/master/concepts/managed-resources">}})
+Read the [managed resources]({{<ref "../concepts/managed-resources">}})
 documentation for more information on configuring resources and storing
 connection secrets for individual resources. 
 {{< /hint >}}

content/v1.18/getting-started/provider-aws.md

@@ -23,7 +23,7 @@ This quickstart requires:
 * an AWS account with permissions to create an S3 storage bucket
 * AWS [access keys](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-creds)
 
-{{<include file="/master/getting-started/install-crossplane-include.md" type="page" >}}
+{{<include file="v1.18/getting-started/install-crossplane-include" type="page" >}}
 
 ## Install the AWS provider
 

content/v1.18/getting-started/provider-azure.md

@@ -25,7 +25,7 @@ This quickstart requires:
   [Virtual Network](https://learn.microsoft.com/en-us/azure/virtual-network/)
 * an Azure account with permissions to create an Azure [service principal](https://learn.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object) and an [Azure resource group](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal)
 
-{{<include file="/master/getting-started/install-crossplane-include.md" type="page" >}}
+{{<include file="v1.18/getting-started/install-crossplane-include" type="page" >}}
 
 ## Install the Azure provider
 

content/v1.18/getting-started/provider-gcp.md

@@ -22,7 +22,7 @@ This quickstart requires:
 * GCP [account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys)
 * GCP [Project ID](https://support.google.com/googleapi/answer/7014113?hl=en)
 
-{{<include file="/master/getting-started/install-crossplane-include.md" type="page" >}}
+{{<include file="v1.18/getting-started/install-crossplane-include" type="page" >}}
 
 ## Install the GCP provider
 

content/v1.18/guides/multi-tenant.md

@@ -304,16 +304,16 @@ dedicated control planes to many tenants within a single organization.
 
 
 <!-- Named Links -->
-[managed resources]: {{<ref "../../master/concepts/managed-resources" >}}
+[managed resources]: {{<ref "../concepts/managed-resources" >}}
 [RBAC]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
-[Composition]: {{<ref "../../master/concepts/compositions" >}}
+[Composition]: {{<ref "../concepts/compositions" >}}
 [CustomResourceDefinitions]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
 [Open Policy Agent]: https://www.openpolicyagent.org/
 [Rego]: https://www.openpolicyagent.org/docs/latest/policy-language/
 [Gatekeeper]: https://open-policy-agent.github.io/gatekeeper/website/docs/
 [here]: https://youtu.be/TaF0_syejXc
 [Multiple Source Field patching]: https://github.com/crossplane/crossplane/pull/2093
-[Configuration packages]: {{<ref "../../master/concepts/packages" >}}
+[Configuration packages]: {{<ref "../concepts/packages" >}}
 [OCI images]: https://github.com/opencontainers/image-spec
 [EKS Cluster]: https://github.com/crossplane-contrib/provider-upjet-aws/blob/main/examples/eks/v1beta2/cluster.yaml
 [provider-aws]: https://github.com/crossplane-contrib/provider-upjet-aws

content/v1.18/guides/self-signed-ca-certs.md

@@ -11,7 +11,7 @@ registries, it must be configured to trust the CA and Intermediate certs.
 
 Crossplane needs to be installed via the Helm chart with the 
 `registryCaBundleConfig.name` and `registryCaBundleConfig.key` parameters 
-defined. See [Install Crossplane]({{<ref "../../master/software/install" >}}).
+defined. See [Install Crossplane]({{<ref "../software/install" >}}).
 
 ## Configure
 

content/v1.18/guides/troubleshoot-crossplane.md

@@ -241,7 +241,7 @@ Debugging Composite Resource Definition (XRD) is like debugging Compositions.
 
 You can use install providers in two ways: `configuration.pkg.crossplane.io` and `provider.pkg.crossplane.io`. You can use either one to install providers with no functional differences to providers themselves.
 If you define a `configuration.pkg.crossplane.io` object, Crossplane creates a
-`provider.pkg.crossplane.io` object and manages it. Refer to [the Packages documentation]({{<ref "/master/concepts/packages">}})
+`provider.pkg.crossplane.io` object and manages it. Refer to [the Packages documentation]({{<ref "../concepts/packages">}})
 for more information about Crossplane Packages.
 
 If you are experiencing provider issues, steps below are a good starting point. 
@@ -451,7 +451,7 @@ To follow the references:
 [Pausing Providers]: #pausing-providers
 [Deleting When a Resource Hangs]: #deleting-when-a-resource-hangs
 [Installing Crossplane Package]: #installing-crossplane-package
-[Crossplane package]: /master/concepts/packages/
+[Crossplane package]: ../concepts/packages/
 [Handling Crossplane Package Dependency]: #handling-crossplane-package-dependency
 [semver spec]: https://github.com/Masterminds/semver#basic-comparisons