No support for "-Force" option when upgrading Azure cloud service

I’m using Azure Cloud Services deployment task. Allow upgrade flag is set to true.

When I try to change vmsize (via configuration file) this error happens:

2016-11-11T13:08:40.7295350Z ##[command]Set-AzureDeployment -Upgrade -ServiceName my-service -Package C:\agent\_work\r1\a\MyService.Azure.cspkg -Configuration C:\agent\_work\r1\a\MyServiceConfiguration.Cloud.cscfg -Slot Production -Label 20161111.2 11/11/2016 13:08:36 -ExtensionConfiguration <extensions>
 
2016-11-11T13:09:16.8000754Z ##[error]BadRequest : The role size specified for role MyService.Tasks in the newly uploaded package differs from the role size for this role in the currently deployed service. Changing the size of the role will cause all local data on the role instance to be lost.  Please use the Force flag if you want to allow the loss of local data.

How to include “-Force” flag when using VSTS deployment task?

[mvvsubbu]

Currently this feature is checked in to our development branch. it will be available in next deployment of VSTS which is approximately finishes in 3 - 4 weeks from now. Are you taking about current VSTS deployment or you went ahead and uploaded new version the task?? If you haven’t uploaded then that is expected behaviour only, as the latest changes are not yet deployed to production.

[yezr]

hey for everyone waiting on this the workaround I found was to change the azure deployment slot on my release to ‘Staging’, which is not as worried about ‘local data loss’ 😃, and then swap them through the azure console!