-
Notifications
You must be signed in to change notification settings - Fork 634
Closed
Labels
closed-for-stalenessfeature-requestNew feature or enhancement. May require GitHub community feedback.New feature or enhancement. May require GitHub community feedback.p3This is a minor priority issueThis is a minor priority issueresponse-requestedWaiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.service-apiThis issue is due to a problem in a service API, not the SDK implementation.This issue is due to a problem in a service API, not the SDK implementation.
Description
Describe the feature
wafv2 GetWebACL support ARN instead of requiring Name and Id
Use Case
- cloudfront.getDistributionConfig returns WebACL ARN, eg:
arn:aws:wafv2:us-east-1:1111:global/webacl/Name/Id
- wafv2.getWebACL requires Name, Id
To get CloudFront's associated WebACL, we have to split response ARN into Name and Id.
Using AWS CDK, ARN is not available in synthesize step thus cannot use the normal string split. This will help unblock aws/aws-cdk#32021, few workarounds were tried but no result.
Proposed Solution
wafv2 GetWebACL accept ARN as input. ARN and (Name + Id) should be mutually exclusive
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
SDK version used
latest
Environment details (OS name and version, etc.)
Ubuntu, Node 20
Metadata
Metadata
Assignees
Labels
closed-for-stalenessfeature-requestNew feature or enhancement. May require GitHub community feedback.New feature or enhancement. May require GitHub community feedback.p3This is a minor priority issueThis is a minor priority issueresponse-requestedWaiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.service-apiThis issue is due to a problem in a service API, not the SDK implementation.This issue is due to a problem in a service API, not the SDK implementation.