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
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
Description
Azure Function apps now support being deployed as a docker image within a Linux app service plan. The only primary difference in the underlying ARM properties are the following:
I don't have a PR yet but would like to volunteer to add support for this.
Based on reading the threads for the referenced items its unclear how it would be best to handle the overloaded kind attribute to automatically be built based on other settings.
The default value for kind in function apps is functionapp. If it's a linux app then it becomes functionapp,linux and finally if its a linux container the value is functionapp,linux,container
One option would be to dynamically build up the kind attribute based on inspecting the app_service_plan_id and other related properties.
Another approach vs. continuing with the linux_fx_version approach would be to split this configuration out into a common object with the properties required to configure a container
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 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Mar 5, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
Azure Function apps now support being deployed as a docker image within a Linux app service plan. The only primary difference in the underlying ARM properties are the following:
kind:
functionapp,linux,container
siteProperties/LinuxFxVersion:
DOCKER|{path_to_registry}/{image_name}:{tag}
I don't have a PR yet but would like to volunteer to add support for this.
Based on reading the threads for the referenced items its unclear how it would be best to handle the overloaded
kind
attribute to automatically be built based on other settings.The default value for kind in function apps is
functionapp
. If it's a linux app then it becomesfunctionapp,linux
and finally if its a linux container the value isfunctionapp,linux,container
One option would be to dynamically build up the
kind
attribute based on inspecting the app_service_plan_id and other related properties.Another approach vs. continuing with the
linux_fx_version
approach would be to split this configuration out into a common object with the properties required to configure a containerNew or Affected Resource(s)
Potential Terraform Configuration
References
azurerm_app_service
resource to support thekind
argument #1045, Feature Request: Web App for Containers support #580The text was updated successfully, but these errors were encountered: