Replacing functionapp with app service creates a hybrid resource
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
**Bicep version**
0.9.1
**Describe the bug**
When attempting to replace an existing function app with a containerized app service, the resulting resource becomes a containerized function app (that somehow works!)
**To Reproduce**
1. Initial resource is of type:
`resource site 'Microsoft.Web/sites@2022-03-01' = {
name: 'a name'
kind: 'functionapp,linux'
[...]
}`
2. Replace the existing resource like:
`resource site 'Microsoft.Web/sites@2022-03-01' = {
name: 'a name'
kind: 'app,linux,container'
properties: {
siteConfig: {
linuxFxVersion: 'DOCKER|myregistry/myimage:mytag'
}
}
[...]
}`
3. The resulting resource gets:
"kind": "functionapp,linux,container",
but somehow works, despite being a regular docker container without function app support.
Contributor guide
Research direction
Start by reproducing the replacement using the two Microsoft.Web/sites@2022-03-01 Bicep snippets and inspect the resulting resource kind. Compare the deployed result with the requested app,linux,container configuration; the issue is done when replacing the function app no longer produces functionapp,linux,container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100