-
Notifications
You must be signed in to change notification settings - Fork 457
FUNCTIONS_WORKER_RUNTIME dotnet-isolated can't be changed #10909
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
Comments
The |
The issue occurs when you choose dotnet isolated by mistake and then want to change to the correct runtime for your application. The function app will continue to throw this warning as if the runtime was not changed. Also unable to redeploy the function app as the setting seems to follow the name of the resource. In my case, the app uses "dotnet", but even if i changed from isolated to just dotnet the function app ignores this change. |
The notification should disappear within 24 hours. Are you experiencing something different? At the moment, it doesn't disappear immediately after you resolve the issue. |
Right - Maybe that's just the issue then. It can get abit confusing so if theres a way to more clear notify the user that the notification might persist would increase the user friendlyness. |
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
To be able to change from dotnet-isolated to dotnet.
Actual behavior
Even after changing to dotnet we get the below error:
Known workarounds
Redeploy the function app with a different name. Redeploying with same name will cause the issue to persist.
Related information
Source
module functionApp 'br/public:avm/res/web/site:0.15.0' = {
name: 'functionApp-${uniqueString('functionApp', deployment().name)}'
scope: resourceGroup(resourceGroupConfiguration.name)
params: {
kind: 'functionapp,linux'
name: functionAppConfiguration.name
serverFarmResourceId: serverFarm.outputs.resourceId
appSettingsKeyValuePairs: {
AzureFunctionsJobHost__logging__logLevel__default: 'Trace'
FUNCTIONS_EXTENSION_VERSION: '~4'
FUNCTIONS_WORKER_RUNTIME: 'dotnet'
}
siteConfig: {
appSettings: union(
[
{
name: 'FUNCTIONS_INPROC_NET8_ENABLED'
value: '1'
}
{
name: 'APPINSIGHTS_INSTRUMENTATIONKEY'
value: applicationInsights.outputs.instrumentationKey
}
{
name: 'WEBSITE_RUN_FROM_PACKAGE'
value: '1'
}
{
name: 'WEBSITE_WEBDEPLOY_USE_SCM'
value: 'false'
}
{
name: 'AzureWebJobsStorage'
value: 'DefaultEndpointsProtocol=https;AccountName=${sa.outputs.name};EndpointSuffix=${environment().suffixes.storage};AccountKey=${existingStorageAccount.listKeys().keys[0].value}'
}
{
name: 'WEBSITE_CONTENTAZUREFILECONNECTIONSTRING'
value: 'DefaultEndpointsProtocol=https;AccountName=${sa.outputs.name};EndpointSuffix=${environment().suffixes.storage};AccountKey=${existingStorageAccount.listKeys().keys[0].value}'
}
{
name: 'WEBSITE_CONTENTSHARE'
value: toLower(functionAppConfiguration.name)
}
],
functionAppConfiguration.additionalAppsettings ?? []
)
netFrameworkVersion: '8.0'
ftpsState: 'FtpsOnly'
minTlsVersion: '1.2'
alwaysOn: true
ipSecurityRestrictions: ipSecurityRestrictions
}
httpsOnly: true
virtualNetworkSubnetId: subnet.outputs.subnet.resourceId
managedIdentities: {
systemAssigned: true
userAssignedResourceIds: [
uami.outputs.resourceId
]
}
roleAssignments: [
{
principalId: uami.outputs.principalId
roleDefinitionIdOrName: 'de139f84-1756-47ae-9be6-808fbbe84772' // Website Contributor
}
{
principalId: uami.outputs.principalId
roleDefinitionIdOrName: '4633458b-17de-408a-b874-0445c86b69e6' // Key Vault Secrets User
}
]
storageAccountResourceId: sa.outputs.resourceId
storageAccountUseIdentityAuthentication: false
vnetRouteAllEnabled: true
appInsightResourceId: applicationInsights.outputs.resourceId
}
dependsOn: [rg]
}
The text was updated successfully, but these errors were encountered: