-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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_web_app - current_stack #16222
Comments
I am getting a similar issue where it is not relating to just dot net core. resource "azurerm_windows_web_app" "app-service" {
} this results in the following on the portal... |
Same with
The Azure Portal UI is blank and consequental |
@cliffey272 dotnet + 5.0 works fine from my side, but I .netcore + v3.0 is not behaving as expected and I'm having a future confirmation about it. |
Hi everyone, i am also having problem with docker for the application stack, with this settings:
it seems the application_stack does not saved in the TF state file correctly. So everytime, i run TF plan, it gives me changes. Has anyone the same problem? Thank you very much |
@leandroscardua The version v3.0 is for dotnetcore runtime, not for .net. However, as there is no 3.0 version of .net, we will fix it in the mentioned pr. |
Hey @leandroscardua , good day! Can you do me a favor which is to confirm if the DotNet Core app deployment is functioning well for you now? Thanks a lot! |
Hi @xiaxyi , Really sorry about the delay to answer you here. Thank you and again sorry |
Thanks @leandroscardua .No worries about the delay, take your times |
HI @xiaxyi , I just finished the test, take a look on the results. possible value, based on the terraform output: .dotnet Version 6 (OK)
Version 5 ( OK,) but show the information related to the The selected version 'v5.0' is deprecated. Please consider updating it.
Version 4 ( OK )
Version 3 ( That is the very weired part, when I setup with that option, we still seeing the issue to setup the version 3.
Version 2 ( to be able to setup the version 3.5, you need to user version the number v2.0 on the manifest,) a bit weird to use on that away.
.dotnetcore Version 3.1 ( OK )
Version 5 ( when we set version 5 and dotnetcore, the final configuration will be dotnetcore 3.1 ), a bit weird to use on that away.
Version 6 ( when we set version 6 and dotnetcore, the final configuration will be dotnetcore 3.1 ), a bit weird to use on that away.
I`m not able to use .NET 7 (Preview), and ther version are not matching with the value on the config. possible value, based on the terraform output: |
Thanks @leandroscardua for the feedbacks. version 3.1 is only for dotnet core runtime. I think we better not use it for dotnet framework app:
You may find more dotnot runtime related information in this doc For higher version, we need to specify the stack as dotnet |
Perfect, With that situation, I'm going to close the issue |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Is there an existing issue for this?
Community Note
Terraform Version
1.1.7
AzureRM Provider Version
3.0.2
Affected Resource(s)/Data Source(s)
azurerm_windows_web_app
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The terraform needs to deploy a dotnetcore version 3.1 on the App Service
Actual Behaviour
It is creating the appservice with the version of the dotnetcore blank, with that situation the app service application couldn`t start, we need a manual interversion to add the correct option.
Steps to Reproduce
No response
Important Factoids
No response
References
Looks like the azure api is expecting dotnetcore value on the current_stack field.
After the deployment, you can run a plan to validate this information.
The text was updated successfully, but these errors were encountered: