Skip to content
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

fix(apigateway): id in schema model maps to $id #15113

Merged
merged 2 commits into from
Mar 31, 2022

Conversation

jihndai
Copy link
Contributor

@jihndai jihndai commented Jun 14, 2021

If we specify the id field when defining an Api Gateway Model's schema, it gets mapped to a $id key, which creates an invalid model because it doesn't comply with the DRAFT-04 specification. The specification requires this field to remain named as id.

fixes #14585


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@gitpod-io
Copy link

gitpod-io bot commented Jun 14, 2021

@peterwoodworth peterwoodworth added the @aws-cdk/aws-apigateway Related to Amazon API Gateway label Jun 17, 2021
@nija-at nija-at added effort/small Small work item – less than a day of effort p2 labels Jul 15, 2021
@nija-at nija-at removed their assignment Jul 15, 2021
@rix0rrr rix0rrr added bug This issue is a bug. p2 and removed p2 @aws-cdk/aws-apigateway Related to Amazon API Gateway effort/small Small work item – less than a day of effort bug This issue is a bug. labels Mar 4, 2022
@TheRealAmazonKendra TheRealAmazonKendra changed the title fix(apigateway): incorrect mapping of id in model schema definition fix(apigateway): id in schema model maps to $id Mar 30, 2022
@github-actions github-actions bot added the @aws-cdk/aws-apigateway Related to Amazon API Gateway label Mar 30, 2022
@github-actions github-actions bot added bug This issue is a bug. effort/small Small work item – less than a day of effort labels Mar 30, 2022
Copy link
Contributor

@TheRealAmazonKendra TheRealAmazonKendra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@mergify
Copy link
Contributor

mergify bot commented Mar 30, 2022

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 1e92517
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit ac5a345 into aws:master Mar 31, 2022
@mergify
Copy link
Contributor

mergify bot commented Mar 31, 2022

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@jihndai jihndai deleted the id-compliance-draft04 branch March 31, 2022 15:10
StevePotter pushed a commit to StevePotter/aws-cdk that referenced this pull request Apr 27, 2022
If we specify the `id` field when defining an Api Gateway Model's schema, it gets mapped to a `$id` key, which creates an invalid model because it doesn't comply with the DRAFT-04 specification. The specification requires this field to remain named as `id`.

fixes aws#14585


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-apigateway Related to Amazon API Gateway bug This issue is a bug. effort/small Small work item – less than a day of effort p2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[apigateway] incorrect mapping of id in model schema definition
7 participants