-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
azurerm_windows_function_app
- correcting runtime settings.
#18076
Conversation
46c480b
to
164b66c
Compare
any progress on this one? |
We have been wondering the same thing, it has been quite a while since this issue was opened and the PR submitted. |
azurerm_windows_function_app
: Correcting runtime settings.azurerm_windows_function_app
- correcting runtime settings.
This comment was marked as off-topic.
This comment was marked as off-topic.
Closing as superseded by 19685 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
For windows function app running on Java/ PowerShell runtime stack, we need to set below properties, instead of windowsFxVersion:
For dotnet runtime, since 3.1 is not a valid value for the underlying dotnet clr, we need to save the dotnet version in the windowsFxVersion property. Otherwise, we won't be able to get the information back.
For node app, we should refer to the app_setting {WEBSITE_NODE_DEFAULT_VERSION} property as mentioned in here.
fix #16375
fix #17029
#17173
fix #18947
fix #18998
The .netFrameworkVersion for dotnet_version = 6 isn't set, it's causing the .netframeworkversion sets to the default value 4 and this leads to the custom ~4 in the function runtime field:
fix issue: #16417