-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
boto_s3_bucket.present is not idempotent #33754
Comments
@zerthimon I am able to replicate this. Looks like there needs to be some logic added to ensure its not run again if its already present. Here is my output as well:
|
At least in my case, this seems to be due to an ACL mismatch. When {
u'Grants': [{
u'Grantee': {
u'DisplayName': '<my username>',
u'ID': '<long hex string>',
u'Type': 'CanonicalUser'
},
u'Permission': 'FULL_CONTROL'
}],
u'Owner': {
u'DisplayName': '<my username>',
u'ID': '<long hex string>'
}
} |
I've tried the state with different ACL confgs (to have the same parameters that api returns for the ACL), but couldn't make it run just once. |
@zerthimon & @Ch3LL: My PR #33776 resolved this issue for me. I'm curious whether it works for you two as well. |
Fixed ACL user comparison. Resolves #33754.
@danslimmon Works well for me!
|
Description of Issue/Question
boto_s3_bucket.present falsely detects changes in s3 bucket permissions and applies the state eventhough there are no changes to be made.
Setup
Steps to Reproduce Issue
Run SLS a few times, and see that there are the same changes every run.
Versions Report
The text was updated successfully, but these errors were encountered: