Azure func v4 compatibility #4178
Open
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
Since Azure Function v4, the invocaation context structure has changed. Closes: elastic#3185
Since Azure Function v4, the invocation context structure has changed. Closes: elastic#3185
…tibility' into azure-func-v4-compatibility
trentm
added a commit
that referenced
this pull request
Jan 16, 2025
See https://learn.microsoft.com/en-ca/azure/azure-functions/functions-node-upgrade-v4 This builds on the work in #4178 by @qzxlkj (type that 5 times fast), which provide most of the runtime code fix. The rest of this is adding testing and updated examples and docs. Refs: #4178 Closes: #3185
3 tasks
|
@qzxclkj Thanks very much for this! And my apologies for taking so long to get back to this. Your changes (except for the usage of See #4426 (comment) for a long-ish discussion of why I don't want to use |
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.
Since Azure Function v4, the invocation context structure has changed.
Closes: #3185
Checklist