-
Notifications
You must be signed in to change notification settings - Fork 23.8k
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
Add ChangeSets to cloudformation_info + updates #64571
Conversation
@waffie1 this PR contains the following merge commits: Please rebase your branch to remove these commits. |
@waffie1, just so you are aware we have a dedicated Working Group for aws. |
@waffie1 this PR contains the following merge commits: Please rebase your branch to remove these commits. |
I've renamed the integration testsuite and the tests are failing due to the stack existing. I'm not sure if it didn't delete last time, or perhaps multiple tests are running in parallel. Do I need to randomize resource names to ensure this doesn't happen, or is something else going on? |
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.
In CI multiple tests may run at the same time (aws/2.7 and aws/3.6, or just potentially multiple PRs testing at the same time), looks like you've got that sorted with resource_prefix now (and shippable as a resource prefix should work now in the CI policy).
Looking at the tests in this PR and #65643 I think it makes the most sense to land that one first then rebase these tests onto that. You'll need to rename main.yaml to main.yml before rebasing though, and use the stack from those tests. The python portion of this PR looks good to me, thanks very much for this cleanup and the new tests @waffie1.
Add ability to retrieve stack change sets Update module to use AnsibleAWSModule Update backoff to use new decorator style Updated exceptions to use fail_json_aws Converted outputs to snake_case where appropriate, for cloudformation_info only to preserve cloudformation_facts functionality. Unconverted keys are stack_outputs, stack_parameters, stack_policy, stack_resources, stack_tags and stack_template
aws-terminator permission for cloudformation have the following resource Resource: arn:aws:cloudformation:us-east-1:{{ aws_account_id }}:stack/ansible-test* updating test stack name to match
Add ability to retrieve stack change sets Update module to use AnsibleAWSModule Update backoff to use new decorator style Updated exceptions to use fail_json_aws Converted outputs to snake_case where appropriate, for cloudformation_info only to preserve cloudformation_facts functionality. Unconverted keys are stack_outputs, stack_parameters, stack_policy, stack_resources, stack_tags and stack_template
rename per request
IAM policy in aws-terminator requires the stack name to begin with ansible-test
mistakenly updated when changing topic_name to use resource_prefix. The test is to check the display name, which is what the stack update changes
remove uneeded files using tests from #65643 with added check to validate changeset is present in info when requested
Requested changes have been made. Using tests from #65643 with a cloudformation_info check inserted where those tests were already creating a change set. |
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.
LGTM, thanks @waffie1!
Add ability to retrieve stack change sets
Update module to use AnsibleAWSModule
Update backoff to use new decorator style
Updated exceptions to use fail_json_aws
Converted outputs to snake_case where appropriate, for cloudformation_info only to preserve cloudformation_facts functionality.
Unconverted keys are stack_outputs, stack_parameters, stack_policy,
stack_resources, stack_tags and stack_template
SUMMARY
Added the ability to retrieve stack change sets which will allow me to display details and handle approval/execute from an external pipeline tool.
While I was in there, I made updated many sections of the module according to the latest guidelines. Changes include:
Update module to use AnsibleAWSModule
Update backoff to use new decorator style
Updated exceptions to use fail_json_aws
Converted outputs to snake_case where appropriate, for cloudformation_info only to preserve cloudformation_facts functionality.
Unconverted keys are stack_outputs, stack_parameters, stack_policy,
stack_resources, stack_tags and stack_template
ISSUE TYPE
COMPONENT NAME
cloudformation_info
ADDITIONAL INFORMATION
BEFORE:
AFTER: