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_slot use_32_bit_worker default value does not match docs or default for azurerm_windows_web_app #25224

Closed
1 task done
Jolton opened this issue Mar 12, 2024 · 3 comments · Fixed by #25227

Comments

@Jolton
Copy link

Jolton commented Mar 12, 2024

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 and review the contribution guide to help.

Terraform Version

1.6.3

AzureRM Provider Version

3.92.0

Affected Resource(s)/Data Source(s)

azurerm_windows_web_app_slot, azurerm_windows_web_app

Terraform Configuration Files

provider "azurerm" {
  features {}
}

resource "azurerm_resource_group" "example" {
  name     = "example-resources"
  location = "West Europe"
}

resource "azurerm_service_plan" "example" {
  name                = "example-plan"
  resource_group_name = azurerm_resource_group.example.name
  location            = azurerm_resource_group.example.location
  os_type             = "Windows"
  sku_name            = "P1v2"
}

resource "azurerm_windows_web_app" "example" {
  name                = "example-windows-web-app"
  resource_group_name = azurerm_resource_group.example.name
  location            = azurerm_service_plan.example.location
  service_plan_id     = azurerm_service_plan.example.id

  site_config {}
}

resource "azurerm_windows_web_app_slot" "example" {
  name           = "example-slot"
  app_service_id = azurerm_windows_web_app.example.id

  site_config {}
}

Debug Output/Panic Output

N/A

Expected Behaviour

A windows web app and slot are created and the use_32_bit_worker setting is set to true on both. This is what is documented on as the default for both resources, https://registry.terraform.io/providers/hashicorp/azurerm/3.95.0/docs/resources/windows_web_app_slot#use_32_bit_worker & https://registry.terraform.io/providers/hashicorp/azurerm/3.95.0/docs/resources/windows_web_app#use_32_bit_worker###

Actual Behaviour

The azurerm_windows_web_app is created correctly with use_32_bit_worker = true but the azurerm_windows_web_app_slot has use_32_bit_worker = false

Steps to Reproduce

No response

Important Factoids

No response

References

No response

@xiaxyi
Copy link
Contributor

xiaxyi commented Mar 13, 2024

@Jolton Thanks for raising this issue, there isn't a default value defined for the property use_32_bit_worker under azurerm_windows_web_app_slot, the value varies from different sevice plan. I modified the doc in the linked PR.

@Jolton
Copy link
Author

Jolton commented Mar 13, 2024

In what way does this "value varies from different service plan"? I don't see anything in the service-plan resource related to 32 bit workers. Is it some hidden property on the service-plan sku?

Also is there a reason we can't just set the default to true on the azurerm_windows_web_app_slot resource? As it is right now it's just completely inconstant with the azurerm_windows_web_app resource

Copy link

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 Apr 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants