Allow getting http trigger metadata from (locked)app from spin-http #1690
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rylev
force-pushed
the
http-trigger-metadata
branch
from
2124ead
to
9643047
Compare
lann
approved these changes
Aug 14, 2023
|
If you'd like to rebase, e2e tests should now be running successfully. |
Signed-off-by: Ryan Levick <[email protected]>
rylev
force-pushed
the
http-trigger-metadata
branch
from
9643047
to
40defaf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allows getting http trigger metadata from an app and locked app without needing to pull in the entire
http-triggercrate (by instead using the more lightweightspin_httpcrate).This also extends
LockedAppto be able to easily deserialize metadata based on a given metadata key.