-
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
Return all infos of a VPC peering connection in ec2_vpc_peer module #355
Return all infos of a VPC peering connection in ec2_vpc_peer module #355
Conversation
@stefanhorning Are you still working on this? Since we can't integration test this, it would be helpful to see task output before and after. We would also like to see module docs. If you are willing to, it would be nice to have unit tests for this module. |
Sorry, didn't have time for Ansible stuff for a while, will try to get the TODOs out of the way, perhaps this or next week. |
#501 should add some initial tests that could be built on. |
Thanks @tremble that helps to speed things up! |
e446f8c
to
b2b10fe
Compare
Tests are actually green now, but one still marked as unstable, not sure what to make of that |
The failed / unstable test was a race condition (an _info straight after the making a change returned the previous status). We can ignore it for now. |
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 change itself looks good.
- Please add a changelog fragment
- Please add some integration tests. They don't need to be thorough on every call, but maybe test all values on the accept idempotency test and test
result.vpc_peering_connection.vpc_peering_connection_id == peer_id_1
on the rest.
…elper method in vpc_peer module
@tremble yes, I am actually still on the above mentioned TODOs right now 😉 :
Will also do
|
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.
Minor typo, but otherwise looking good.
Ready for final review now. |
Thanks for your work on this @stefanhorning |
…r module (ansible-collections#355) * Return all infos of a VPC peering connection in ec2_vpc_peer module. * More extensive tests for vpc_peer module. Also got rid of redundant helper method in vpc_peer module This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections@faa7d64
…nsible-collections#355) * Return all infos of a VPC peering connection in ec2_vpc_peer module. * More extensive tests for vpc_peer module. Also got rid of redundant helper method in vpc_peer module
…nsible-collections#355) * Return all infos of a VPC peering connection in ec2_vpc_peer module. * More extensive tests for vpc_peer module. Also got rid of redundant helper method in vpc_peer module
…nsible-collections#355) * Return all infos of a VPC peering connection in ec2_vpc_peer module. * More extensive tests for vpc_peer module. Also got rid of redundant helper method in vpc_peer module
Cloudformation: use is_boto3_error_message Reviewed-by: https://github.com/apps/ansible-zuul
SUMMARY
While boto3 returns a whole lot of useful information on a VPC peering connection, this module threw those away and only returned the ID. This PR changes that to pass through all information, which is also quite valuable when updating routing tables etc.
ISSUE TYPE
COMPONENT NAME
ec2_vpc_peer module
ADDITIONAL INFORMATION