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
As Cluster Admin I want a feature So that I can import existing buckets(resources) into a crossplane resource
According to crossplane documentation it should be possible to import existing resources. https://docs.crossplane.io/latest/guides/import-existing-resources/
When creating a bucket with the required annotation crossplane.io/external-name currently the bucket fails to sync with the error ``
crossplane.io/external-name
Bucket spec:
apiVersion: minio.crossplane.io/v1 kind: Bucket metadata: annotations: crossplane.io/external-name: bucket-local-dev name: bucket-local-dev spec: deletionPolicy: Delete forProvider: {} managementPolicies: - '*' providerConfigRef: name: provider-config
Error Message: "observe failed: bucket already exists, try changing bucket name: bucket-local-dev"
Versions:
No response
The text was updated successfully, but these errors were encountered:
Is there any way to do this with the current version or does this require effort to implement to the operator?
Sorry, something went wrong.
No branches or pull requests
Summary
As Cluster Admin
I want a feature
So that I can import existing buckets(resources) into a crossplane resource
Context
According to crossplane documentation it should be possible to import existing resources. https://docs.crossplane.io/latest/guides/import-existing-resources/
When creating a bucket with the required annotation
crossplane.io/external-name
currently the bucket fails to sync with the error ``Bucket spec:
Error Message: "observe failed: bucket already exists, try changing bucket name: bucket-local-dev"
Versions:
Out of Scope
No response
Further links
No response
Acceptance Criteria
No response
Implementation Ideas
No response
The text was updated successfully, but these errors were encountered: