Incorrect Documentation, Cannot Update existing Cloud Service

[TrevSAU]

Documentation is incorrect for New-AzCloudService. It cannot be used to update a Cloud service (though that is the premise of the first sentence). The script will throw an error if the Cloud Service exists.

---

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7ac3e71b-7d9e-c221-08d2-fe4770905281
• Version Independent ID: fc9ecdfd-2ead-37c5-b12c-eaa2224edb74
• Content: New-AzCloudService (Az.CloudService)
• Content Source: src/CloudService/help/New-AzCloudService.md
• Service: azure-powershell
• GitHub Login: @dcaro
• Microsoft Alias: dcaro

[dingmeng-xue]

Thanks for reporting. That description is generated from PUT method of Rest API. We should correct them.

Please use Update-AzCloudService for update operation.

[Aokrip]

Hello,

Is there any command that would act as New-AzCloudService for update? Update-AzCloudService does not support the same parameters (for config file, definition, package...) as New-AzCloudService.

Is something like Set-AzCloudService, with the same parameters possibility as New-AzCloudService existing? What is the limitation there?

[dingmeng-xue]

Hi Aokrip,

New version of cmdlets just use New for creation and Update for updating parameters. It can help to reduce the confusion. which parameter do you want to update? We will look into it.

[Aokrip]

Hi @dingmeng-xue,

I am looking for a way to update the whole Configuration of a Cloud Service by passing a new cscfg file (As it's done on the Azure Portal). I am also thinking for the same regaring Service Definition and Package.
To recap, it would be the following parameters: -ConfigurationFile, -PackageFile and -DefinitionFile
When we deploy a release, we used to override completely the configuration of the Cloud Service, to make sure all changes are taken in account.

Maybe it's not the way it's supposed to work, please let me know :)

Thanks and regards,

[Aokrip]

Hello @dingmeng-xue

Did you have a chance to have a look at my comment above? Should I post it somewhere else ?

Thanks and regards,

Cyril

[dingmeng-xue]

If just talking about documentation, it is a design issue of Autorest.PowerShell from the beginning. I have created issue to improve it Azure/autorest.powershell#899

For cmdlet behavior, we need your team's help and provide a script and environment for our further analysis.