-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Split AWS Config modules #40111
Split AWS Config modules #40111
Conversation
@ryansb this PR contains more than one new module. Please submit only one new module per pullrequest. For further explanation, please read grouped module documentation |
Thanks @ryansb. As a general rule, is the preferred pattern here to err on the side of keeping modules small and specific vs large and comprehensive? I actually have an AWS Storage Gateway module that's pretty much done but it's very much like my large AWS Config module. If keeping modules small is preferred then I'll go ahead and break that one up too before I submit it. |
The test
|
@slapula Yeah, generally we prefer to go small and then let the modules grow with the services. We used to do bigger modules (like |
The test
The test
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great.
register: output | ||
ignore_errors: yes | ||
|
||
# - assert: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The commented out assertions in the always
could be removed.
bot_status |
Componentslib/ansible/modules/cloud/amazon/aws_config_aggregation_authorization.py lib/ansible/modules/cloud/amazon/aws_config_aggregator.py lib/ansible/modules/cloud/amazon/aws_config_delivery_channel.py lib/ansible/modules/cloud/amazon/aws_config_recorder.py lib/ansible/modules/cloud/amazon/aws_config_rule.py test/integration/targets/aws_config/aliases test/integration/targets/aws_config/defaults/main.yaml test/integration/targets/aws_config/files/config-trust-policy.json test/integration/targets/aws_config/tasks/main.yaml test/integration/targets/aws_config/templates/config-s3-policy.json.j2 Metadatawaiting_on: ryansb |
!needs_revision |
@ryansb Why is the It looks like it probably should be |
* Adding module for AWS Config service * adding integration tests * Split resource types into their own modules * Properly use resource_prefix and retry on IAM "eventual consistency" * Add config aggregator module * AWS config aggregator integration test fixes * AWS config recorder module * Config aggregation auth rule * Use resource_prefix in IAM role name * Disable config tests
* Adding module for AWS Config service * adding integration tests * Split resource types into their own modules * Properly use resource_prefix and retry on IAM "eventual consistency" * Add config aggregator module * AWS config aggregator integration test fixes * AWS config recorder module * Config aggregation auth rule * Use resource_prefix in IAM role name * Disable config tests
SUMMARY
Takes the single big module proposed by @slapula #39080 and pulls them into smaller modules for easier docs/usage.
These are all in one PR for now, but I can pull them apart
ISSUE TYPE
COMPONENT NAME
AWS Config
ANSIBLE VERSION
ADDITIONAL INFORMATION