Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[in-proc backport] Fallback behavior to ensure in-proc payload compatibility with dotnet-isolated as the FUNCTIONS_WORKER_RUNTIME value #10439 #10449

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

kshyju
Copy link
Member

@kshyju kshyju commented Sep 4, 2024

in-proc backport of #10439

…t-isolated` as the `FUNCTIONS_WORKER_RUNTIME` value (#10439)

* Adding diagnostic warning/error when function worker runtime does not match with deployed payload

* Making the new condition specific to "dotnet-isolated" worker to reduce impact.

* Adding a test

* PR feedback fixes

* Missed release notes in last push

* Removed an unnecessary code change.

* Minor cleanup

* Minor cleanup- made a method private and vairable renaming

* Updating HostingConfig test to reflect the new hosting config property addition.

* PR Feedback updates.

* Fix test to reflect renaming changes from PR feedback.
@kshyju kshyju requested a review from a team as a code owner September 4, 2024 21:38
@kshyju kshyju merged commit bb017c5 into in-proc Sep 4, 2024
10 checks passed
@kshyju kshyju deleted the shkr/10439_2 branch September 4, 2024 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants