Skip to content
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

provider/aws: Fix issue with Route 53 and pre-existing, external Hosted zones #1415

Merged
merged 1 commit into from
Apr 8, 2015

Conversation

catsby
Copy link
Contributor

@catsby catsby commented Apr 7, 2015

Fixes #1405 by always cleaning the zone_id we use. If it's externally provided and users use the full ID /hostedzone/xxxxx, we weren't trimming the prefix off.

@phinze
Copy link
Contributor

phinze commented Apr 8, 2015

LTGM

catsby added a commit that referenced this pull request Apr 8, 2015
provider/aws: Fix issue with Route 53 and pre-existing, external Hosted zones
@catsby catsby merged commit 9a3bc12 into master Apr 8, 2015
@catsby catsby deleted the b-fix-route53-recorcd-zone branch April 8, 2015 14:39
@ghost
Copy link

ghost commented May 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Route53 resource : InvalidSignatureException
2 participants