You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Skip validation of FUNCTIONS_WORKER_RUNTIME with function metadata in placeholder mode (#10459)
* Excluding WarmUp function during placeholder mode when validating FWR with Language in funciton metadata.
* Simplified the change based on PR feedback.
* Cancelled another change which is needed due to simplification.
* Adding a check in `ValidateAndLogRuntimeMismatch` to ensure it is called only during non placeholder mode code path. If called form placeholder mode, this method will throw now.
* Checking error log level in tests.
// Ensure customer deployed application payload matches with the worker runtime configured for the function app and log a warning if not.
777
777
// If a customer has "dotnet-isolated" worker runtime configured for the function app, and then they deploy an in-proc app payload, this will warn/error
778
778
// If there is a mismatch, the method will return false, else true.
thrownewInvalidOperationException($"Validation of '{EnvironmentSettingNames.FunctionWorkerRuntime}' with deployed payload metadata should not occur in placeholder mode.");
// this dotnet isolated specific logic is temporary to ensure in-proc payload compatibility with "dotnet-isolated" as the FUNCTIONS_WORKER_RUNTIME value.
Copy file name to clipboardExpand all lines: test/WebJobs.Script.Tests.Integration/WebHostEndToEnd/WebJobsStartupEndToEndTests.cs
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ public async Task InProcAppsWorkWithDotnetIsolatedAsFunctionWorkerRuntimeValue()
66
66
"which does not match the worker runtime metadata found in the deployed function app artifacts. "+
67
67
"The deployed artifacts are for 'dotnet'. See https://aka.ms/functions-invalid-worker-runtime "+
68
68
"for more information. The application will continue to run, but may throw an exception in the future.";
69
-
Assert.Single(fixture.Host.GetScriptHostLogMessages(), p =>p.FormattedMessage!=null&&p.FormattedMessage.EndsWith(expectedLogEntry));
69
+
Assert.Single(fixture.Host.GetScriptHostLogMessages().Where(a =>a.Level==Microsoft.Extensions.Logging.LogLevel.Warning), p =>p.FormattedMessage!=null&&p.FormattedMessage.EndsWith(expectedLogEntry));
0 commit comments