You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
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
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.
Is there an existing issue for this?
Community Note
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
Debug Output/Panic Output
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
The text was updated successfully, but these errors were encountered: