We have a worker role cloud service setup and deployed initially at the Windows Azure portal. Subsequently we attempted to deploy using powershell cmdlet Publish-AzureServiceProject, and it breaks complaining it cannot find the intended deployment name.
PS D:\Projects\Socket> Publish-AzureServiceProject
VERBOSE: Publishing to Windows Azure. This may take several minutes...
VERBOSE: 7:15:06 PM - Preparing runtime deployment for service 'devsocket'
VERBOSE: 7:15:06 PM - Preparing deployment for devsocket with Subscription ID:
<GUID>...
VERBOSE: 7:15:29 PM - Connecting...
VERBOSE: 7:15:32 PM - Uploading Package to storage service devstore...
VERBOSE: 7:15:39 PM - Upgrading...
Publish-AzureServiceProject : "An exception occurred when calling the ServiceManagement API. HTTP Status Code: 404.
Service Management Error Code: ResourceNotFound. Message: The deployment name 'productionDeploy' does not exist..
Operation Tracking ID: a3385dc1efa142b792480ec484f42685."
At line:1 char:1
+ Publish-AzureServiceProject
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (:) [Publish-AzureServiceProject], ServiceManagementClientException
+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Management.CloudService.Cmdlet.PublishAzureServiceProjectCommand
"productionDeploy" is not something we specified in the initial deployment, and not sure how to tell the cmdlet to use something else. There appears to be no parameter we can use in deploymentSettings.json to influence this.
How can we adjust this? thanks
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral