When creating a VpcLattice Rule via API / CLI you can specify any HTTP request method, as per VPC Lattice docs. When creating the resource via CloudFormation currently an error is received if the method is not in an allowed set of enum values. This does not include PATCH, or allow for custom values.
Expected Behavior
Method property on AWS::VpcLattice::Rule HttpMatch should accept any string value.
Observed Behavior
Currently allowed values are CONNECT | DELETE | GET | HEAD | OPTIONS | POST | PUT | TRACE as per CloudFormation docs.
Test Cases
Pass PATCH as the Method:
#/Match/HttpMatch/Method: #: only 1 subschema matches out of 2
#/Match/HttpMatch/Method: failed validation constraint for keyword [enum]
Name of the resource
Other
Resource Name
AWS::VpcLattice::Rule
Issue Description
When creating a VpcLattice Rule via API / CLI you can specify any HTTP request method, as per VPC Lattice docs. When creating the resource via CloudFormation currently an error is received if the method is not in an allowed set of enum values. This does not include
PATCH
, or allow for custom values.Expected Behavior
Method property on AWS::VpcLattice::Rule HttpMatch should accept any string value.
Observed Behavior
Currently allowed values are
CONNECT | DELETE | GET | HEAD | OPTIONS | POST | PUT | TRACE
as per CloudFormation docs.Test Cases
Pass
PATCH
as the Method:Other Details