feat(route53): Convenience API for creating zone delegations #1853
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When creating delegation relationship between two
PublicHostedZone
s,one can now use
zone.addDelegation(otherZone)
instead of manuallycreating the
ZoneDelegationRecord
insteance. This reduces the risk ofpassing the incorrect name server, or hosting the record on the wrong
end of the relationship (DNS is hard!)
Additionally, fixes a bug in which it was not possible to create a zone
delegation record using a
IHostedZone.hostedZoneNameServers
propertyas the array was mapped, which caused the
Fn::GetAtt
stringified listtoken to become corrupted.
Fixes #1847
Pull Request Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.