You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.
There seems to be a bug in the CloudFormation schema file at CloudFormationV1.schema for resource AWS::EC2::VPC property InstanceTenancy which is described with a type of Number but lists strings for its allowed-values -- here's the snippet:
"InstanceTenancy": {
"type": "Number",
"allowed-values": [
"default",
"dedicated"
],
"required": false,
"description": "The allowed tenancy of instances launched into the VPC. A value of \"default\" means instances can be launched with any tenancy; a value of \"dedicated\" means instances must be launched with tenancy as dedicated."
},
I'm submitting this ticket here, although I'm not sure it's the correct forum. I know that there has been some other discussion related to the schema file in #14.
If this is the not the correct mechanism to submit requests related to the CFN schema file, please advise.
The text was updated successfully, but these errors were encountered:
Incidentally, the User Guide description of this resource, lists this property as String type so it looks like this is just a mix up in the schema file.
Found another deviation for the resource AWS::EC2::Route as described here. The schema is missing a property NatGatewayId which allows you to add a route to a NAT Gateway resource. Without this property, you can't route to a NAT Gateway using CloudFormation templates.
There seems to be a bug in the CloudFormation schema file at CloudFormationV1.schema for resource
AWS::EC2::VPC
propertyInstanceTenancy
which is described with a type ofNumber
but lists strings for itsallowed-values
-- here's the snippet:I'm submitting this ticket here, although I'm not sure it's the correct forum. I know that there has been some other discussion related to the schema file in #14.
If this is the not the correct mechanism to submit requests related to the CFN schema file, please advise.
The text was updated successfully, but these errors were encountered: