feat: add delegation_record to route53 resolver rule #43282
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.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
No changes to security controls.
Description
With
DELEGATE
a new rule type for Route53 resolver rules has been introduced. The sectionReferences
contains links to What`s new article and CloudFormation docs.DELEGATE
as rule type, we need to make thedomain_name
argument optional:DELEGATE
requires adelegation_record
containing the DNS name.UpdateResolverRule
does not allow to update thedelegation_record
, hence weForceNew
on changes todelegation_record
.ListResolverRules
does not support to filter fordelegation_record
, hence the filter expression in the data source is not updated.Relations
Closes #43239
References
Delegate
in AWS SDK Go v2Output from Acceptance Testing
Data source