[Service Connector] Fix PostgreSQL passwordless connection not working because of deprecated command

[wchigit]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az webapp/containerapp connection create postgres-flexible --user-identity client-id=XX subs-id=XX --source-id XX --target-id XX
az webapp/containerapp connection create postgres-flexible --system-identity -source-id XX --target-id XX

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

Hi @wchigit,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[Copilot]

Pull Request Overview

This PR replaces deprecated ad-admin commands with the new microsoft-entra-admin subcommands for PostgreSQL passwordless connections.

• Update list call to use microsoft-entra-admin instead of ad-admin
• Update create call to use microsoft-entra-admin instead of ad-admin

Comments suppressed due to low confidence (1)

src/serviceconnector-passwordless/azext_serviceconnector_passwordless/_credential_free.py:693

• No tests currently validate that the new microsoft-entra-admin commands are invoked correctly. Add unit tests for set_user_admin to ensure the right CLI strings are constructed.

admins = run_cli_cmd('az postgres flexible-server microsoft-entra-admin list -g "{}" -s "{}" --subscription "{}"'.format(

[github-actions]

Hi @wchigit

Release Suggestions

Module: serviceconnector-passwordless

• Update VERSION to 3.3.2 in src/serviceconnector-passwordless/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema

[wchigit]

@kairu-ms Could you take a look at this? Why am I having trouble updating the version? THX

[AllyW]

@kairu-ms Could you take a look at this? Why am I having trouble updating the version? THX

@wchigit the issue comes from the unsuccessful release from last version 3.3.2: #8688

The latest official release version is still 3.3.1 https://github.com/Azure/azure-cli-extensions/releases?q=serviceconnector-&expanded=true therefore in this pr, it only allows 3.3.2.

[AllyW]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[wchigit]

@kairu-ms Could you take a look at this? Why am I having trouble updating the version? THX

@wchigit the issue comes from the unsuccessful release from last version 3.3.2: #8688

The latest official release version is still 3.3.1 https://github.com/Azure/azure-cli-extensions/releases?q=serviceconnector-&expanded=true therefore in this pr, it only allows 3.3.2.

Thanks for reply. The version should be updated to 3.3.2 in this PR: #8688. Was there a reason why this is not released? @AllyW

[wangzelin007]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[AllyW]

@kairu-ms Could you take a look at this? Why am I having trouble updating the version? THX

@wchigit the issue comes from the unsuccessful release from last version 3.3.2: #8688
The latest official release version is still 3.3.1 https://github.com/Azure/azure-cli-extensions/releases?q=serviceconnector-&expanded=true therefore in this pr, it only allows 3.3.2.

Thanks for reply. The version should be updated to 3.3.2 in this PR: #8688. Was there a reason why this is not released? @AllyW

Pipeline got stuck by setuptools updates and pipeline didn't get triggered as expected. Confirm with @wangzelin007 in teams channel.

[wangzelin007]

At that time, setuptools was upgrading and caused many of our CI failures. We were working on pinning the setuptools version, so I didn't notice that the release had failed.
I did receive the release failed Teams notification though.