-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Wavelength Zones as valid Availability Zones attributes #1966
Comments
list being sourced from https://github.com/aws-cloudformation/cfn-python-lint/blob/master/src/cfnlint/data/ExtendedSpecs/all/03_value_types.json Available Wavelength zones are probably going to be too frequently updated to manually maintain. Which property type? Also can workaround with resource-level ignores until this is fixed |
Who maintains 03_value_types.json? Just wanted to make sure available Wavelength Zones were matched to the available Local Zones, which also expects to change throughout the year. In terms of property type, this would be the AvailabilityZone attribute for a subnet resource -- is this what you had in mind? |
* Lambda runtime deprecation updates (aws-cloudformation#2033) https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-function.html#cfn-lambda-function-runtime * switching AvailabilityZone from AllowedValues to AllowedPatternRegex fixes aws-cloudformation#1966 https://aws.amazon.com/blogs/aws/now-open-third-availability-zone-in-the-aws-china-beijing-region/ Co-authored-by: Pat Myron <PatMyron@users.noreply.github.com>
cfn-lint version: (
cfn-lint --version
) Latest (v0.48.1)Description of issue. When creating CloudFormation template for resources in a Wavelength Zones, I get a warning
"You must specify a valid allowed value for [Attribute] (us-west-2-wl1-sea-wlz-1). Valid values are ["af-south-1a","af-south-1b"....]"
I'm requesting support that the full list of Wavelength Zones be added to the list of valid availability zones, which are:
The text was updated successfully, but these errors were encountered: