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

azurerm_windows_web_app site config application stack is not in alignment with the supported versions #19850

Closed
1 task done
vj-msft opened this issue Jan 4, 2023 · 4 comments
Labels

Comments

@vj-msft
Copy link

vj-msft commented Jan 4, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

1.3.6

AzureRM Provider Version

3.37.0

Affected Resource(s)/Data Source(s)

azurerm_windows_web_app

Terraform Configuration Files

application_stack {
      current_stack  = try(var.site_config.runtime_stack, "dotnet")
      dotnet_version = try(var.site_config.dotnet_version, "v4.8")
    }

Debug Output/Panic Output

Error: expected site_config.0.application_stack.0.dotnet_version to be one of [v2.0 v3.0 core3.1 v4.0 v5.0 v6.0 v7.0], got v4.8

Expected Behaviour

Based on the portal experience, the current supported dotnet version for windows web app is
image

So expected terraform module to accept the same dotnet versions.

Actual Behaviour

Based on the documentation the terraform module currently accepts the below versions but few are not supported or available in windows web app.
dotnet_version - (Optional) The version of .NET to use when current_stack is set to dotnet. Possible values include v2.0,v3.0,core3.1, v4.0, v5.0, v6.0 and v7.0.

Steps to Reproduce

No response

Important Factoids

No response

References

No response

@vj-msft vj-msft added the bug label Jan 4, 2023
@github-actions github-actions bot removed the bug label Jan 4, 2023
@jackofallops
Copy link
Member

Hi @vj-msft - Thanks for opening this issue.
Unfortunately the values displayed in the portal and those actually used by the API do not align 1:1. Currently the service maps the values as:

Portal Value API value
ASP.NET V3.5 v2.0
ASP.NET V4.8 v4.0
.NET 6 (LTS) v6.0
.NET 7 (STS) v7.0

These are reflected in #19685 and I'm adding the supporting documentation notes to this at the moment.

Hope this helps!

@vj-msft
Copy link
Author

vj-msft commented Jan 4, 2023

Thank you @jackofallops. This helps.

@jackofallops
Copy link
Member

Thanks @vj-msft - I'm going to close this one out for now since it will be addressed by the above PR 👍

@github-actions
Copy link

github-actions bot commented Feb 4, 2023

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants