03/19/2021, 1:53 PM
I have a question for proper way to use Pulumi in conjuction with app service slots. My typical deployment before Pulumi was to first update the binaries on a slot, warm up the app, and then swap the slot. Most of the Pulumi examples for app service show using
and specifying a blob storage url for deployment. When using Azure Pipelines to build my app and then deploying via same or Octopus Deploy, etc., I already have my binaries so uploading them to a storage account is a little redundant. If I wanted to achieve a similar process with Pulumi - what is the recommendation? If it matters I am using dotnet.


03/19/2021, 6:47 PM
For what it's worth, we've split the infra and code deployments so that pulumi creates the infra and the slots, then the code is deployed separately using a separate pipeline that runs a separate slot switch action.