Question: How can I set up a development and production environment using deployment slots in the existing Azure App Service?

[jeannotdamoiseaux]

How can I set up a development and production environment using deployment slots in the existing Azure App Service? I want to use deployment slots to create a separation between development and production environments for this application. Specifically, I’d like to deploy changes to the development slot for testing without affecting the production environment and manually swap the tested deployment to the production slot once verified. Are there any specific configurations or steps in this template to support this workflow? For example, how do I deploy to a specific slot (e.g., using azd up)?

[jeannotdamoiseaux]

For instance, where in the configuration or workflow should I indicate that the app should be deployed to a specific slot, such as the development slot, when using commands like azd up?

[jeannotdamoiseaux]

For instance, where in the configuration or workflow should I indicate that the app should be deployed to a specific slot, such as the development slot, when using commands like azd up?

I tried adding
--slot
to
azd deploy --no-prompt in azure-dev.yml (line 130)
, but that doesn't seem to work.

[pamelafox]

The azd CLI doesn't yet have built-in support for deployment slots, as far as I'm aware. See the various related issues here:
https://github.com/Azure/azure-dev/issues?q=is%3Aissue%20state%3Aopen%20%22deployment%20slot%22
Did you see --slot in documentation somewhere?

I believe the current recommendation is to use different azd environments with two different App Service instances (but the rest the same, via azd env variables).

cc @vhvb1989 from the azd team

[jeannotdamoiseaux]

The azd CLI doesn't yet have built-in support for deployment slots, as far as I'm aware. See the various related issues here: https://github.com/Azure/azure-dev/issues?q=is%3Aissue%20state%3Aopen%20%22deployment%20slot%22 Did you see --slot in documentation somewhere?

I believe the current recommendation is to use different azd environments with two different App Service instances (but the rest the same, via azd env variables).

cc @vhvb1989 from the azd team

Ironically, ChatGPT hallucinated this command, and it felt quite natural/logical to me. Unfortunate that it doesn't exist, because having two separate webapps is not very convenient or reliable. Perhaps ChatGPT came up with a new feature?

[pamelafox]

It would be a very appreciated feature, as the developer experience for safely deploying a new version is currently subpar. Perhaps you could leave comments on one or both of the issues as to what experience you would like?
Azure/azure-dev#2373
Azure/azure-dev#383