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
In LocalStack API Gateway, we currently have a specific path-style format to call
execute-api
:http(s)://<your-domain>:<port>/restapis/<api_id>/<stage>/_user_request_/<your-path>
.The actual AWS format is this, with the host:
http(s)://<api-id>.execute-api.<domain>/<stage>/<your-path>
There are multiple problems with our current "path style" format:
This PR introduces a new path format for API Gateway, available with the "Next Gen" provider:
http(s)://<your-domain>:<port>/_aws/apigateway/execute-api/<api-id>/<stage>/<your-path>
This new format follows the same order as AWS, is clearer about the LocalStack-only part, is on the
_aws
namespace, and has execute-api in the name, which maps to the URL people are used to see.It also sets up a deprecation path for the previous "path style" and log a message when people uses it with the new provider. We will also need to update the documentation accordingly.
Deprecation message:
Changes
_user_request_
endpoint when using the NG provder