We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
The example Composition manifest in https://docs.crossplane.io/v1.13/getting-started/provider-aws-part-2/#create-a-deployment-template has 2 similar patches for the bucket and the dynamodb table. The one for the bucket uses location and the one for table uses spec.location.
location
spec.location
I suspect though that they should actually both use spec.location given the XRD defined in https://docs.crossplane.io/v1.13/getting-started/provider-aws-part-2/#apply-the-api.
bucket:
patches: - type: FromCompositeFieldPath fromFieldPath: "location" toFieldPath: "spec.forProvider.region"
table:
patches: - type: FromCompositeFieldPath fromFieldPath: "spec.location" toFieldPath: "spec.forProvider.region"
URL: https://docs.crossplane.io/v1.13/getting-started/provider-aws-part-2/
The text was updated successfully, but these errors were encountered:
Fixed with #552
Sorry, something went wrong.
No branches or pull requests
The example Composition manifest in https://docs.crossplane.io/v1.13/getting-started/provider-aws-part-2/#create-a-deployment-template has 2 similar patches for the bucket and the dynamodb table. The one for the bucket uses
location
and the one for table usesspec.location
.I suspect though that they should actually both use
spec.location
given the XRD defined in https://docs.crossplane.io/v1.13/getting-started/provider-aws-part-2/#apply-the-api.bucket:
table:
URL: https://docs.crossplane.io/v1.13/getting-started/provider-aws-part-2/
The text was updated successfully, but these errors were encountered: