Deployment always tries to create a blobContainer

[cternes]

When deploying with the DeploymentManager, I always get the following error:
BlobCommand: container or blob already exists!

Problem is, that always a blob container with the name “elastadeploy” will be created. If the container already exists, the deployment will fail with the above error.

[PaulGauthier]

We ran into a similar issue and found another approach that may work for you.

We have a section of code that will upload a new package, only when an update is needed:

var blobClient = new BlobClient(_subscriptionId, "elastadeploy", "myStorageAccount", _certificate);
blobClient.DeleteBlob("myPackage.cspkg");
blobClient.CreateAndUploadBlob("myPackage.cspkg", @"C:\Azure\Deployment\Packages\myPackage.cspkg");

Then we just deploy straight from the blob storage:

deploymentManager.AddCertificate(_certificate)
                .ForNewDeployment("myDeployment")
                .SetCspkgEndpoint(@"http://myStorageAccount.blob.core.windows.net/elastadeploy/myPackage.cspkg", @"C:\Azure\Deployment\Configuration\ServiceConfiguration.Cloud.cscfg")
                .WithExistingHostedService("myHostedService")
                .WithStorageAccount("myStorageAccount")
                .AddEnvironment(DeploymentSlot.Production)
                .AddParams(DeploymentParams.StartImmediately)
                .ForRole("myRole")
                .WithInstanceCount(1)
                .WaitUntilAllRoleInstancesAreRunning()
                .Go()
                .Commit();

Hope this helps.

[azurecoder]

Thanks for pointing this out. I've updated this now so that it won't try and create "elastadeploy" if it exists already.