Skip to content

fix(apigatewayv2): Invalid mapping key value#9141

Merged
mergify[bot] merged 12 commits intoaws:masterfrom
pahud:apigv2-mapping-key-fix
Jul 21, 2020
Merged

fix(apigatewayv2): Invalid mapping key value#9141
mergify[bot] merged 12 commits intoaws:masterfrom
pahud:apigv2-mapping-key-fix

Conversation

@pahud
Copy link
Copy Markdown
Contributor

@pahud pahud commented Jul 17, 2020

  • mappingKey is now optional
  • undefinied mappingKey indicates the root base path mapping for custom domain
  • ensure the resource dependency for the api mapping and stage

Fixes: #8983


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

@pahud pahud changed the title fix(apigatewayv2): Invalid stage identifier specified fix(apigatewayv2): Invalid mapping key value Jul 18, 2020
@mergify mergify bot dismissed ericzbeard’s stale review July 21, 2020 02:22

Pull request has been modified.

@pahud pahud requested a review from ericzbeard July 21, 2020 02:44
@pahud pahud marked this pull request as draft July 21, 2020 03:00
@pahud
Copy link
Copy Markdown
Contributor Author

pahud commented Jul 21, 2020

I need update my regex pattern. WIP now.

@pahud pahud marked this pull request as ready for review July 21, 2020 03:52
@pahud
Copy link
Copy Markdown
Contributor Author

pahud commented Jul 21, 2020

Hi @ericzbeard

I am ready now. Please take a look again.

Copy link
Copy Markdown
Contributor

@ericzbeard ericzbeard 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
Copy Markdown
Contributor

mergify bot commented Jul 21, 2020

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
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
  • Commit ID: 7a2e522
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

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

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jul 21, 2020

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).

@mergify mergify bot merged commit c88ad5f into aws:master Jul 21, 2020
Chriscbr pushed a commit to Chriscbr/aws-cdk that referenced this pull request Jul 23, 2020
- `mappingKey` is now optional
-  undefinied `mappingKey` indicates the root base path mapping for custom domain
-  ensure the resource dependency for the api mapping and stage

Fixes: aws#8983

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
curtiseppel pushed a commit to curtiseppel/aws-cdk that referenced this pull request Aug 11, 2020
- `mappingKey` is now optional
-  undefinied `mappingKey` indicates the root base path mapping for custom domain
-  ensure the resource dependency for the api mapping and stage

Fixes: aws#8983

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
mergify bot pushed a commit that referenced this pull request Aug 26, 2021
…6204)


fix(apigatewayv2): fix api mapping key too strict issue.

This PR fix the issue that Validation of apiMappingKey in ApiMappingProps is too strict.

Closes: #15948 

----
# Considerations:

The validation rule of the apiMappingKey was added in [PR #9141](#9141) to fix [issue #8983](#8983). 

However, as time changed, it looks like the validation rules have changed as well.
But the validation rules are not clearly written out in AWS documentation, so I did [various validations](#15948 (comment)) in the AWS console based on the unit test, and found the rules to be very complex.

Thanks to @pahud and @nija-at 's suggestions, there is no need to stand in the way between CDK users and API Gateway supporting more possibilities in the future, I just removed the validation logic and the relative unit tests.

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
hollanddd pushed a commit to hollanddd/aws-cdk that referenced this pull request Aug 26, 2021
…s#16204)


fix(apigatewayv2): fix api mapping key too strict issue.

This PR fix the issue that Validation of apiMappingKey in ApiMappingProps is too strict.

Closes: aws#15948 

----
# Considerations:

The validation rule of the apiMappingKey was added in [PR aws#9141](aws#9141) to fix [issue aws#8983](aws#8983). 

However, as time changed, it looks like the validation rules have changed as well.
But the validation rules are not clearly written out in AWS documentation, so I did [various validations](aws#15948 (comment)) in the AWS console based on the unit test, and found the rules to be very complex.

Thanks to @pahud and @nija-at 's suggestions, there is no need to stand in the way between CDK users and API Gateway supporting more possibilities in the future, I just removed the validation logic and the relative unit tests.

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
TikiTDO pushed a commit to TikiTDO/aws-cdk that referenced this pull request Sep 6, 2021
…s#16204)


fix(apigatewayv2): fix api mapping key too strict issue.

This PR fix the issue that Validation of apiMappingKey in ApiMappingProps is too strict.

Closes: aws#15948 

----
# Considerations:

The validation rule of the apiMappingKey was added in [PR aws#9141](aws#9141) to fix [issue aws#8983](aws#8983). 

However, as time changed, it looks like the validation rules have changed as well.
But the validation rules are not clearly written out in AWS documentation, so I did [various validations](aws#15948 (comment)) in the AWS console based on the unit test, and found the rules to be very complex.

Thanks to @pahud and @nija-at 's suggestions, there is no need to stand in the way between CDK users and API Gateway supporting more possibilities in the future, I just removed the validation logic and the relative unit tests.

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
david-doyle-as24 pushed a commit to david-doyle-as24/aws-cdk that referenced this pull request Sep 7, 2021
…s#16204)


fix(apigatewayv2): fix api mapping key too strict issue.

This PR fix the issue that Validation of apiMappingKey in ApiMappingProps is too strict.

Closes: aws#15948 

----
# Considerations:

The validation rule of the apiMappingKey was added in [PR aws#9141](aws#9141) to fix [issue aws#8983](aws#8983). 

However, as time changed, it looks like the validation rules have changed as well.
But the validation rules are not clearly written out in AWS documentation, so I did [various validations](aws#15948 (comment)) in the AWS console based on the unit test, and found the rules to be very complex.

Thanks to @pahud and @nija-at 's suggestions, there is no need to stand in the way between CDK users and API Gateway supporting more possibilities in the future, I just removed the validation logic and the relative unit tests.

*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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[@aws-cdk/aws-apigatewayv2] Httpapi not deploying when new stack created when using custom domain

4 participants