Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix broken links in documentation #220

Merged
merged 1 commit into from
Dec 1, 2023
Merged

Fix broken links in documentation #220

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/Configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ You can setup the Terraform Provider using AWS [IAM Roles for Service Accounts
For more information, check out the example
[setup](../examples/aws-eks-irsa-setup.yaml), the process is similar to what you
would use for the
[provider-aws](https://github.com/upbound/provider-aws/blob/master/AUTHENTICATION.md#using-iam-roles-for-serviceaccounts).
[provider-aws](https://github.com/upbound/provider-aws/blob/main/AUTHENTICATION.md#authentication-using-irsa).

## Provider Performance and Throughput

Expand Down Expand Up @@ -353,5 +353,5 @@ spec:
```

At Vault side configuration is also needed to allow the write operation, see
[example](https://crossplane.io/docs/v1.9/guides/vault-as-secret-store.html#prepare-vault)
[example](https://docs.crossplane.io/knowledge-base/integrations/vault-as-secret-store/)
here for inspiration.
9 changes: 4 additions & 5 deletions docs/MigrationGuide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ kubectl apply -f op-providerconfig.yaml
providerconfig.tf.upbound.io/default created
```

#### 5. Pause community provider following https://crossplane.io/docs/v1.10/reference/troubleshoot.html#pausing-providers
#### 5. Pause community provider by following instructions at https://docs.crossplane.io/knowledge-base/guides/troubleshoot/#pausing-providers

```bash
kubectl get providers crossplane-provider-terraform -o yaml > community-provider-terraform.yaml
Expand All @@ -100,10 +100,9 @@ kubectl -n upbound-system get deploy|grep crossplane-provider-terraform
crossplane-provider-terraform-e56e83bb443a 0/0 0 0 24m
```

#### 6. If the Workspace resources are instantiated as a part of Composition, pause
the associated Claim or XR using the
https://crossplane.io/docs/v1.10/reference/composition.html#pause-annotation,
e.g.
#### 6. If the Workspace resources are instantiated as a part of Composition:

[Pause the associated Claim or XR](https://docs.crossplane.io/latest/concepts/composite-resources/#pausing-composite-resources) by running:

```bash
kubectl annotate terraformclaim.example.upbound.io/iam-role-demo-001 crossplane.io/paused=true
Expand Down