az-devops-service-endpoint-update leaves much to be desired

[rupamroy2006]

Describe the bug

I am wondering what exactly can be updated using the update command. I would like to update the password of the service connection here by using the below mentioned azure CLI command but it looks like there is no way to get to it other than deleting the service connection and re-creating it. I would rather not prefer this approach since it invalidates my pipeline. I would expect the command : az devops service-endpoint update to provide a --data or --set argument.

Related command

az devops service-endpoint update --id <service_id> .....

Errors

unrecognized arguments: --set

Issue script & Debug output

az devops service-endpoint update --id <id_number> --set
az devops service-endpoint update --id <id_number> --data

Expected behavior

I would expect that updating the content of the service connection should be supported and not just the metadata. This would be a step in the Azure pipeline definition.

Environment Summary

azure-cli 2.49.0

core 2.49.0
telemetry 1.0.8

Extensions:
azure-devops 0.26.0

Dependencies:
msal 1.20.0
azure-mgmt-resource 22.0.0

Additional context

I am working in a big software organisation where this is going to be a blocker for our organisation wide adoption of ADO.

[yonzhan]

Thank you for opening this issue, we will look into it.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @v-anvashist, @V-hmusukula.

Issue Details

---

Describe the bug

I am wondering what exactly can be updated using the update command. I would like to update the password of the service connection here by using the below mentioned azure CLI command but it looks like there is no way to get to it other than deleting the service connection and re-creating it. I would rather not prefer this approach since it invalidates my pipeline. I would expect the command : az devops service-endpoint update to provide a --data or --set argument.

Related command

az devops service-endpoint update --id <service_id> .....

Errors

unrecognized arguments: --set

Issue script & Debug output

az devops service-endpoint update --id <id_number> --set
az devops service-endpoint update --id <id_number> --data

Expected behavior

I would expect that updating the content of the service connection should be supported and not just the metadata. This would be a step in the Azure pipeline definition.

Environment Summary

azure-cli 2.49.0

core 2.49.0
telemetry 1.0.8

Extensions:
azure-devops 0.26.0

Dependencies:
msal 1.20.0
azure-mgmt-resource 22.0.0

Additional context

I am working in a big software organisation where this is going to be a blocker for our organisation wide adoption of ADO.

Author:	rupamroy2006
Assignees:	-
Labels:	bug, customer-reported, Service Attention, DevOps
Milestone:	-

[rupamroy2006]

@yonzhan : Could you please get someone to look into this issue? We are waiting for a resolution on this to push forward the token renewal setup and has an impact on our release quality. Many thanks in advance for looking in this.

[Arvindgade]

Hi @yonzhan,We checked the issue and we are not owning the above functionality.

[rupamroy2006]

@yonzhan : Has there been some movement on this? This is really blocking for us and we would like to automate the entire key rotation stuff. Saving the rotated password back to the same service connection is an important step in our initiative. Many thanks in advance..

[jessehouwing]

You should now be able to use the Workload Identity Federation features to not have to rely on service connections as much.

The Azure DevOps cli team's repo can be found here:
https://github.com/Azure/azure-devops-cli-extension

Their bug tracker is on the Visual Studio Developer Community:
https://github.com/Azure/azure-devops-cli-extension/issues/new/choose

[jessehouwing]

The REST API for service endpoints is pretty well documented, so you could rely on

Az API

Or

Az DevOps invoke

To call the API directly.