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
Describe the bug
I initially opened a discussion here: Azure/bicep#13172
But did not get much assistance, so opening a bug here to track. When redeploying a Bicep template deployment involving a Microsoft.Web/sites section, it appears to clear all Deployment Center deployments, effectively resetting the site to default content.
Expected: when redeploying via Bicep template, previous Deployment Center content remains intact.
To Reproduce
Deploy template with Microsoft.Web/sites configuration
Deploy AppService via Azure DevOps content
Repeat step 1
Observe AppService deployed in step 2 has been erased and reset to standard AppService content
Additional context
Thank you for all your effort out there. Outside of this one issue everything else works exactly as expected/desired. 🙏
The text was updated successfully, but these errors were encountered:
The interesting thing that I just encountered here is that this does not seem to apply to slots. 🤔 I did a deployment just now that deployed to both sites and slots and only the sites was cleared.
I am surprised this hasn't gotten more activity. Is it truly expected behavior that each deployment destroys a website's content? 🤔 This seems a bit disruptive and counter-intuitive, especially if the deployment is part of CD/CI.
Bicep version
Describe the bug
I initially opened a discussion here: Azure/bicep#13172
But did not get much assistance, so opening a bug here to track. When redeploying a Bicep template deployment involving a
Microsoft.Web/sites
section, it appears to clear all Deployment Center deployments, effectively resetting the site to default content.Expected: when redeploying via Bicep template, previous Deployment Center content remains intact.
To Reproduce
Microsoft.Web/sites
configurationAdditional context
Thank you for all your effort out there. Outside of this one issue everything else works exactly as expected/desired. 🙏
The text was updated successfully, but these errors were encountered: