-
Notifications
You must be signed in to change notification settings - Fork 398
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
Stabilize ec2_eip module #936
Stabilize ec2_eip module #936
Conversation
Build succeeded.
|
result = { | ||
'changed': changed | ||
} | ||
module.exit_json(**result) | ||
|
||
result['changed'] |= ensure_ec2_tags( |
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.
Since allocate_address supports TagsSpecifications (https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2.html#EC2.Client.associate_address), you can directly add the tags on creation instead of after associating the ip. Just have a look here for example https://github.com/ansible-collections/amazon.aws/pull/531/files
TagSpecifications
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.
not available until 1.19.41
While we should be able to support this in 4.0.0 (1.20.0 was released Feb 2021), it's not something we officially support yet. I'd recommend pulling this into a separate PR
Build succeeded.
|
Can you also please have a look at this #159 and link it if your changes solve the bugs? |
I commented out unstable and I wasn’t having issues… I wanted to see how it performed in CI first. I didn’t make any changes that would’ve fixed that afaik. |
@jatorcasso if you want to see if the stability of the tests has improved I run the tests on the CI account from my local system in a screen or tmux session (with history size set to something very large, like 10,000,000 lines so you can review failures no matter how far back they are) with a shell script like this, to see if any failures are produced over a large number of executions:
|
Build succeeded (gate pipeline).
|
backport-3: Stabilize ec2_eip module (#936) Backport into stable-3 of #936 with commit id: d0596e3 SUMMARY fixed check_mode issues added integration tests for check_mode / idempotency updated json returned when state = absent for clarity removed json_query references fixes #159 Depends-On: ansible-collections/amazon.aws#672 ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_eip Reviewed-by: Mark Woolley Reviewed-by: Mark Chappell Reviewed-by: Alina Buzachis Reviewed-by: Joseph Torcasso Reviewed-by: Jill R SUMMARY ISSUE TYPE Bugfix Pull Request Docs Pull Request Feature Pull Request New Module Pull Request COMPONENT NAME ADDITIONAL INFORMATION
Stabilize ec2_eip module SUMMARY fixed check_mode issues added integration tests for check_mode / idempotency updated json returned when state = absent for clarity removed json_query references fixes ansible-collections#159 Depends-On: ansible-collections/amazon.aws#672 ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_eip Reviewed-by: Mark Woolley <[email protected]> Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: Joseph Torcasso <None> Reviewed-by: Jill R <None> This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections@d0596e3
SUMMARY
state = absent
for clarityDepends-On: ansible-collections/amazon.aws#672
ISSUE TYPE
COMPONENT NAME
ec2_eip