Repository navigation
Default behavior of aws_s3 overwrite #762
Description
Summary
I believe the default behavior of the aws_s3 module should be overwrite: different instead of always in order for the module to be idempotent by default. Every time the module runs with its current default behavior, ansible shows that something has changed. Usually a module will report no changes if ran multiple times by default.
Issue Type
Feature Idea
Component Name
aws_s3
Additional Information
Code of Conduct
- I agree to follow the Ansible Code of Conduct
Activity
ansibullbot commentedon Mar 30, 2022
Files identified in the description:
plugins/modules/aws_s3.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/aws_s3.py)If these files are inaccurate, please update the
component namesection of the description or use the!componentbot command.click here for bot help
ansibullbot commentedon Mar 30, 2022
cc @jillr @linabuzachis @lwade @s-hertel @tremble
click here for bot help
goneri commentedon Apr 5, 2022
It's a good idea but it's also a breaking change. We should wait for a 3.0 release to introduce a change like this.
aws_s3 - ensure overwrite: different (#811)
aws_s3 - ensure overwrite: different (ansible-collections#811)
add `KmsMasterKeyId` as attribute option for boto3 call (ansible-coll…
add `KmsMasterKeyId` as attribute option for boto3 call (ansible-coll…
add `KmsMasterKeyId` as attribute option for boto3 call (ansible-coll…
ci(deps): bump the github-actions group with 7 updates (#3048)