feat(route53resolver): improve FirewallRuleGroup import by name #33787
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.
Issue
Closes #16335.
Reason for this change
Currently,
FirewallRuleGroup
allows importing an existing rule group by ID usingfromFirewallRuleGroupID()
, but there is no built-in way to reference an existing rule group by name. Users need to implement their own lookup logic via the AWS SDK. This change provides a direct method to import a firewall rule group by name, simplifying the process.Description of changes
FirewallRuleGroup.fromFirewallRuleGroupName()
, which allows users to import a firewall rule group using its name instead of just an ID.Describe any new or updated permissions being added
None
Description of how you validated changes
Checklist
Acknowledgments
Thanks to @arvchahal for collaboration on this feature!
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license