azure functionapp update does not properly handle the --slot setting

[dannmichelson]

Describe the bug
When the trying to update properties for a Azure Function Slot (specifically the loadBalancing property) using Azure CLI, the change is applied to the production slot rather than the slot specified

To Reproduce
ex: az functionapp update -g $resourceGroup -n $name -s $slotName --set siteConfig.loadBalancing=PerSiteRoundRobin

Expected behavior
The expectation is that properties for the $slotName slot is updated.

Environment summary
run in Powershell Core 7.1.3, Azure CLI 2.31.0

Additional context
The biggest reason this is a big problem is that we change all our configuration in our staging slot and then swap into the main slot, which ensures no down time during deployments.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ahmedelnably, @fabiocav.

Issue Details

---

Describe the bug
When the trying to update properties for a Azure Function Slot (specifically the loadBalancing property) using Azure CLI, the change is applied to the production slot rather than the slot specified

To Reproduce
ex: az functionapp update -g $resourceGroup -n $name -s $slotName --set siteConfig.loadBalancing=PerSiteRoundRobin

Expected behavior
The expectation is that properties for the $slotName slot is updated.

Environment summary
run in Powershell Core 7.1.3, Azure CLI 2.31.0

Additional context
The biggest reason this is a big problem is that we change all our configuration in our staging slot and then swap into the main slot, which ensures no down time during deployments.

Author:	dannmichelson
Assignees:	-
Labels:	Service Attention, Functions, customer-reported
Milestone:	-

[yonzhan]

route to service team

[dannmichelson]

Any updates on this?

[dannmichelson]

I'm still seeing this issue. This should be a bigger deal because people may be intending to modify a staging slot but end up modifying their production slot, causing unexpected production restarts!!

[navba-MSFT]

@dannmichelson Apologies for the late reply. The similar issue was discussed here too where the PR #21698 has been filed and its is merged now. Could you please test using the most recent version of the CLI and check if you are still facing the same issue ? Awaiting your reply.