Skip to content
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.

CloudFormation schema correction #38

Closed
ebekker opened this issue Apr 5, 2016 · 3 comments
Closed

CloudFormation schema correction #38

ebekker opened this issue Apr 5, 2016 · 3 comments
Labels
bug We can reproduce the issue and confirmed it is a bug. cloud-formation

Comments

@ebekker
Copy link

ebekker commented Apr 5, 2016

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.

@ebekker
Copy link
Author

ebekker commented Apr 5, 2016

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.

@ebekker
Copy link
Author

ebekker commented Apr 8, 2016

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.

@zhangzhx zhangzhx added cloud-formation bug We can reproduce the issue and confirmed it is a bug. labels Oct 25, 2016
@zhangzhx
Copy link
Contributor

This has been corrected. Thanks for reporting this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug We can reproduce the issue and confirmed it is a bug. cloud-formation
Projects
None yet
Development

No branches or pull requests

2 participants