-
Notifications
You must be signed in to change notification settings - Fork 56
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
[AWS::ApiGatewayV2::Integration] - [BUG] - Breaking changes in schema for ApiGatewayV2 Integration #2114
Comments
From CFN team: There was an update to Integration that was rolled back in IAD due to some breaking changes for customers. We expect a slightly-modified version of the schema to be rolled out again in the next week or 2, this time with backward compatibility for the breaking changes. |
I'll also follow up with the doc writer to make sure any changes are properly represented in the public CFN documentation. For now, in IAD, the old schema (
|
Name of the resource
AWS::ApiGatewayV2::Integration
Resource Name
No response
Issue Description
The CloudFormation schema downloaded from https://schema.cloudformation.us-east-1.amazonaws.com/CloudformationSchema.zip started to have substantial changes for the
AWS::ApiGatewayV2::Integration
resource since August 23rd. None of these changes are represented in the CloudFormation docs here: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-apigatewayv2-integration.html#cfn-apigatewayv2-integration-responseparameters.In detail:
ResponseParameter
andResponseParameterList
definitions are no longer present. Instead theResponseParameters
property is simply of typeobject
now.RequestParameters
andRequestTemplates
properties also lost theirpatternProperties
and are simply of typeobject
now as well.IntegrationId
property has been renamed toId
.ApiId
property is no longer a primary identifierAre those changes expected?
Expected Behavior
No breaking changes to the existing schema:
Observed Behavior
Test Cases
n/a
Other Details
No response
The text was updated successfully, but these errors were encountered: