-
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
Feature Request: please add the ability to specify site_config in azurerm_function_app #745
Comments
hey @dcherniv Thanks for opening this issue :) So that we can look into this (as there's differences between the App Service site config and a Function App site config) - would it be possible to know which fields are you looking to use within the Thanks! |
@tombuildsstuff use_32_bit_worker_process is probably more important because for me when function_app was provisioned with the following, it defaulted to 32 bit workers for some odd reason.
|
I'd add client_affinity_enabled as well: https://www.terraform.io/docs/providers/azurerm/r/app_service.html#client_affinity_enabled This is very important in the context of Functions which are served behind an API management resource: |
always_on is now supported thanks to |
Issue #745, adds more options to azurerm_function_app
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
azurerm_app_service supports site_config options. Since functions is essentially an app_service, please add the ability to specify site_config for it.
Without this, there's no way to control things like 32/64 bit workers and others.
The text was updated successfully, but these errors were encountered: