-
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
Remove 'ResourceRecords' when 'AliasTarget' #502
Conversation
i think this fix resolves #434 (sorry, didn't look closely enough at bug reports before making a PR) my familiarity with this code is minimal, but it works on my machine :) |
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.
Thanks for taking the time to open this PR. A couple of things
- Sanity tests are failing due to extra spaces in the 'empty' line you added.
- Please add a changelog: https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to
- To reduce the chance of a regression, please a test to our integration tests: tests/integration/targets/route53/tasks/
sending a change to the route53 api that includes both an AliasTarget and a ResourceRecord causes the api to return with an error. removing the ResourceRecord when an AliasTarget is preset allows this module to continue without error
@boutetnico @Surgo I've tweaked the PR and added some tests. Could you try out the latest version from this PR? |
@tremble I've tested your changes. They allowed me to spot a mistake in my playbook, I was using the |
recheck |
Approved with all checks passing. |
@notatoad Thanks for your original submission |
* Remove 'ResourceRecords' when 'AliasTarget' sending a change to the route53 api that includes both an AliasTarget and a ResourceRecord causes the api to return with an error. removing the ResourceRecord when an AliasTarget is preset allows this module to continue without error * Cleanup tests and use RFC2602 Domains and RFC5737 CIDRs * Add integration test for aliases * Make Alias and TTL mutually exclusive * Update docs to list region/failover/weight as mutually exclusive. * changelog
* Remove 'ResourceRecords' when 'AliasTarget' sending a change to the route53 api that includes both an AliasTarget and a ResourceRecord causes the api to return with an error. removing the ResourceRecord when an AliasTarget is preset allows this module to continue without error * Cleanup tests and use RFC2602 Domains and RFC5737 CIDRs * Add integration test for aliases * Make Alias and TTL mutually exclusive * Update docs to list region/failover/weight as mutually exclusive. * changelog
* Remove 'ResourceRecords' when 'AliasTarget' sending a change to the route53 api that includes both an AliasTarget and a ResourceRecord causes the api to return with an error. removing the ResourceRecord when an AliasTarget is preset allows this module to continue without error * Cleanup tests and use RFC2602 Domains and RFC5737 CIDRs * Add integration test for aliases * Make Alias and TTL mutually exclusive * Update docs to list region/failover/weight as mutually exclusive. * changelog
* Remove 'ResourceRecords' when 'AliasTarget' sending a change to the route53 api that includes both an AliasTarget and a ResourceRecord causes the api to return with an error. removing the ResourceRecord when an AliasTarget is preset allows this module to continue without error * Cleanup tests and use RFC2602 Domains and RFC5737 CIDRs * Add integration test for aliases * Make Alias and TTL mutually exclusive * Update docs to list region/failover/weight as mutually exclusive. * changelog This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections@8a2a138
SUMMARY
sending a change to the route53 api that includes both an AliasTarget and a ResourceRecord causes the api to return with an error. removing the ResourceRecord when an AliasTarget is present allows this module to successfully modify an alias record
ISSUE TYPE
COMPONENT NAME
route53
ADDITIONAL INFORMATION
calling the following
results in the following error:
the attached change removes the 'ResourceRecord' from the ChangeBatch, and the record is created without error