-
Notifications
You must be signed in to change notification settings - Fork 362
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.
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
Removing notificationConfiguration from s3 bucket config doesn't remove it from the bucket. #1140
Comments
Can confirm that Issue persists with |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
/fresh Observing this in |
I have a branch where I have fixed an associated issue (allowing TopicARN updates). I may also try to resolve this. |
What happened?
I created a bucket with a notifications queue and wanted to remove the queue -- removing the notificationConfiguration field did not remove it from the bucket. Adding
notificationConfiguration: {}
Caused crossplane to fill in the current bucket configuration.Is there a way to remove the notification configuration through the crossplane provider?
How can we reproduce it?
What environment did it happen in?
Crossplane version:
1.6.1 of crossplane -- 1.21.1 of the AWS provider
The text was updated successfully, but these errors were encountered: