refactor(WAF): Rename WAF
to WAFRegional
and Add Global WAF
Service
#5389
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.
Context
I identified a misconception in how the AWS WAF services and clients were referenced and utilized across our services. Specifically,
AWS WAFRegional
was being referred to as simplyWAF
, which led to confusion. Additionally,AWS WAF
(global) was not represented separately, which could cause potential issues when differentiating between global and regional WAF services.Description
This PR addresses the following:
WAF
service and client have been renamed toWAFRegional
to align with AWS’s naming convention for regional WAF services.WAF
service and client have been introduced to representAWS WAF
(global), ensuring that both regional and global WAF services are distinctly covered.This change mirrors the structure used by AWS and is similar approach to how we handle
S3
andS3Control
services under the same S3 service file with different client files.Checklist
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.