-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix SSH into VMs without public IP #6126
Conversation
Hi @dionhaefner, |
Thank you for your contribution dionhaefner! We will review the pull request and get back to you soon. |
SSH |
Could you please add test for this case? |
Please write the description of PR change into the |
@zhoxing - There are no scenario tests for this extension at the moment, and I don't think there is an easy way to test this logic simply with unit tests. This part of the code is currently untested by automated tests, which is something that I've been planning on addressing soon. |
@dionhaefner I have submitted a PR for this suggestion in your branch https://github.com/dionhaefner/azure-cli-extensions/tree/patch-1 to save your time. Could you please approve it so that it can be reviewed again here ? |
Update HISTORY.md
Update setup.py
Merged, thanks! 👍 |
Pull in changes to history
@microsoft-github-policy-service agree |
[Release] Update index.json for extension [ ssh ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=47919&view=results |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
Without the fix:
With the fix:
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?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
.