Skip to content

Missing deployment slot support for az functionapp update #15800

@kevin-secrist

Description

@kevin-secrist

Describe the bug

Hi there!

When attempting to update one of the properties on my function app, I found that az functionapp update does not have slot support. To attempt to work around this I tried using az webapp (which does have slot support) but it gave me an error telling me to use az functionapp instead.

Other commands that may/may not need slot support:

az functionapp config hostname get-external-ip
az functionapp deployment user set
az functionapp deployment user show
az functionapp devops-pipeline create
az functionapp function *

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

az functionapp update --resource-group <rg> --name <app> --slot staging --set siteConfig.healthCheckPath=/api/HealthCheck

Errors:

az: error: unrecognized arguments: --slot staging

To reiterate, az webapp update does have slot support.

A separate issue that I don't need addressed is that passing in the resourceId of the slot gets ignored, e.g.

az functionapp update --ids /subscriptions/{SubscriptionId}/resourceGroups/{ResourceGroup}/providers/Microsoft.Web/sites/{FunctionApp}/slots/staging --set siteConfig.healthCheckPath=/api/HealthCheck

Ends up silently updating the production slot instead of the staging slot. I imagine this is probably the behavior across all commands though. This is undesired behavior because it will cause an app restart on the production slot when an out-of-rotation slot should have been updated+restarted instead.

Expected Behavior

Update the config on the slot as expected in the same way that it does on the production slot.

Environment Summary

Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.11.0 *

Extensions:
front-door 1.0.9

Additional Context

Thanks for your help!

Metadata

Metadata

Assignees

Labels

Functionsaz functionappService AttentionThis issue is responsible by Azure service team.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions