APIGW: validate REST API custom id tag #12539
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
When setting a custom id for a REST API and using the
_custom_id_
tag, using an hyphen will make the API fail because the routing won't work, as the regex explicitly doesn't match hyphens:<regex('[^-]+'):api_id>
, to avoid matching on the-vpce
part.It would fail silently, because it wouldn't be able to find the API.
We now validate the custom id to not allow
-
character in it.Note: maybe another solution would be to adapt the regex to allow hyphens, but didn't want to take the risk to change it, and this has been the behavior since this has been introduced.
Changes