azurerm_linux_function_app - add flex consumption feature.
#27531
Conversation
github-actions
bot
added
documentation
service/app-service
size/XL
waiting-response
and removed
size/XS
labels
|
Very excited for this PR! Please review team :) |
| } else { | ||
| appSettings = updateOrAppendAppSettings(appSettings, "AzureWebJobsStorage", storageString, false) | ||
| if storageString != "" { | ||
| appSettings = updateOrAppendAppSettings(appSettings, "FUNCTIONS_EXTENSION_VERSION", version, false) |
There was a problem hiding this comment.
Please do not add this FUNCTIONS_EXTENSION_VERSION app setting for Flex Consumption function apps. It will eventually be blocked for Flex Consumption apps and is not required. The runtime version that this conveyed for other hosting plans is now handled automatically by the platform for Flex Consumption.
There was a problem hiding this comment.
This is set conditionally on regular function app, not the flex one
| Type: pluginsdk.TypeInt, | ||
| Optional: true, | ||
| Default: 2048, | ||
| ValidateFunc: validation.IntInSlice([]int{512, 2048, 4096}), |
There was a problem hiding this comment.
This list might not be true for all regions, and we might introduce new instance sizes in the future. The actual list per region comes from the Stacks API but that is dynamic, not sure if we can use it in terraform to validate right? So here we have to decide:
- Do we not validate and let the user put any number (which if they put incorrectly will show a control plane exception)
- Or do we put the current list here of all possible current instance sizes here, and then keep updating the list of values as new instance sizes are introduced?
There was a problem hiding this comment.
From our perspective, we would rather have new sizes available immediately and a control plane exception kick up, rather than having to wait for the AzureRM team to fix it each time a new size is available. My vote is for option 1 (no validation).
There was a problem hiding this comment.
removed the restriction.
|
Hello, any ETA for this to be released? We just got a meeting with one of your Azure ACE and he recommended to use Flex Consumption plans. We can create the resources manually but we are using terraform. |
|
Please 🚢 ❤️ |
Community Note
Description
Support azure function running in azure flex consumption plan
PR Checklist
For example: “
resource_name_here- description of change e.g. adding propertynew_property_name_here”Changes to existing Resource / Data Source
Testing
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_resource- support for thething1property [GH-00000]This is a (please select all that apply):
Related Issue(s)
Fixes #0000
Note
If this PR changes meaningfully during the course of review please update the title and description as required.