Use isolated worker model in e2e test functions app #647
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I received an email saying, "Beginning 10 November 2026, the in-process model for .NET apps in Azure Functions will no longer be supported."
The Functions app we create for the end-to-end tests uses the in-process model, and in fact is running on .NET 6, which is EOL. This Functions app needs a refresh generally, so I added a few (untested) changes to the script that generates the app, as a placeholder to visit later.
Handy links:
Migrate .NET apps from the in-process model to the isolated worker model
az functionapp reference
Develop Azure Functions locally using Core Tools
Azure Functions Core Tools reference