Nothing to add on this topic?
So far this is my understanding on programmatically managing sticky App Settings, and it's quite disappointing:
- It can't be done with ARM templates
- It can't be done with Az PowerShell module
- It can be done with Azure PowerShell module, which will be deprecated and is being replaced by Az module mentionned above. The worst part is that Azure Powershell module requires the account used to be administrator or co-administrator of the subscription when Contributor on the Web App should be enough. This poses a security question.
Microsoft, we need something like Set-AzWebApp -SlotStickyAppSettingNames
, and Set-AzWebApp -SlotStickyConnectionStringNames
please!
Slots enable new, safer and more agile deployments, this is great, having sticky App Settings and Connection Strings is needed, so thanks for that, but lack of ability to manage them programmatically (unless done with a solution being deprecated and requiring exagerately high privileges) is a blocker to industrial / large scale use!