Reorg and docs for aws lambda and HTTP (API Gateway HTTP vs. REST API) #15052
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.
There are no code changes. Only directory and artifact renames:
AWS has two separate API Gateway APIs. HTTP and REST. This is implemented in two separate quarkus extensions. As stated on the dev list, it just doesn't make sense to put everything into one quarkus extension. There are different deployment scripts (sam.yaml), a different lambda json protocol, and there is not any shared runtime code. While the same microservice could be deployed to either Gateway API, the developer will have to redeploy their service anyways. Its not like they can change an environment variable and respin an instance. So again, I kept them as separate extensions.