Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring back way to swap webapp slots (e.g. ActiveSlot) #632

Open
dornfeder opened this issue Mar 5, 2021 · 3 comments
Open

Bring back way to swap webapp slots (e.g. ActiveSlot) #632

dornfeder opened this issue Mar 5, 2021 · 3 comments
Labels
impact/missing-api kind/enhancement Improvements or new features missing-api/post Resources or functionality that is not supported automatically because it relies on POST endpoints.

Comments

@dornfeder
Copy link

In the old "azure" package, there is a resource named ActiveSlot that let you swap a webapp slot to production. In the new "azure-native" package, I am missing that resource, and could not find any other in the docs that lets me do a swap.

Unless I did completely miss something, please bring back the ActiveSlot resource or a different way of swapping a slot to production. Alternatively, if there is a new way to swap slots that i could not find, please document it in a way so that it can be found.

Thank you.

@dornfeder dornfeder added the kind/enhancement Improvements or new features label Mar 5, 2021
@mikhailshilkov
Copy link
Member

It's a fair ask. We don't support it currently because WebApps_SwapSlotWithProduction is a POST operation and it doesn't really fit into our resource model automatically.

We'll track this for future improvements. For now, you'd have to use an Azure SDK from your Pulumi program to accomplish this.

@mikhailshilkov mikhailshilkov added impact/missing-api kind/enhancement Improvements or new features and removed kind/enhancement Improvements or new features labels Mar 5, 2021
@dornfeder
Copy link
Author

Thanks for the info. Then I will use the old azure package for doing the swap, for the time being.

@sergioalen
Copy link

Hi guys, just on this one. You can achieve this with ARM templates by setting the buildVersion and targetBuildVersion properties, if the target build version is not the same to the build version it performs the swap. https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots#example-resource-manager-template

I can't find these properties in the azure native interface nor docs.

@thomas11 thomas11 added the missing-api/post Resources or functionality that is not supported automatically because it relies on POST endpoints. label Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/missing-api kind/enhancement Improvements or new features missing-api/post Resources or functionality that is not supported automatically because it relies on POST endpoints.
Projects
None yet
Development

No branches or pull requests

4 participants