Skip to content

Conversation

@mcnealm13
Copy link
Contributor

@mcnealm13 mcnealm13 commented Mar 20, 2025


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

Related command

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:

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
Copy link

Validation for Breaking Change Starting...

Thanks for your contribution!

@azure-client-tools-bot-prd
Copy link

Hi @mcnealm13,
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.

@yonzhan
Copy link
Collaborator

yonzhan commented Mar 20, 2025

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

@github-actions
Copy link

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>

@github-actions
Copy link

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

@github-actions
Copy link

Hi @mcnealm13

Release Suggestions

Module: ssh

  • Please log updates into to src/ssh/HISTORY.rst
  • Update VERSION to 2.0.7 in src/ssh/setup.py

Notes

Comment on lines +219 to +242
if (len(active_directory_graph_api_array) == 4):
scope_postfix = (
active_directory_graph_api_array[1]
+ "."
+ active_directory_graph_api_array[2]
+ "."
+ active_directory_graph_api_array[3]
)
# special case for USNat
elif len(active_directory_graph_api_array) == 5:
scope_postfix = (
active_directory_graph_api_array[1]
+ "."
+ active_directory_graph_api_array[2]
+ "."
+ active_directory_graph_api_array[3]
+ "."
+ active_directory_graph_api_array[4]
)
else:
raise azclierror.InvalidArgumentValueError(
f"Unsupported cloud {cmd.cli_ctx.cloud.name.lower()}",
"Supported clouds include azurecloud,azurechinacloud,azureusgovernment")
scope = f"https://pas.{scope}/CheckMyAccess/Linux/.default"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The scope_postfix variable doesn't seem to be used in the new scope

@Alex-AZPS
Copy link

@vthiebaut10 can you review again ? CC @anwarnuma

Copy link
Member

@jiasli jiasli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

String manipulation is too fragile. I don't favor the solution proposed by this PR.

@jiasli
Copy link
Member

jiasli commented Jul 31, 2025

Previously the SSH auth scope is hard-coded in Azure PowerShell, and later it leverages "Environment" to store the scope to support new sovereign clouds:

This approach makes sense to me. We can add --ssh-auth-scope when registering a cloud, such as

az cloud register --ssh-auth-scope "https://pas.windows.net/CheckMyAccess/Linux/.default

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants