-
Notifications
You must be signed in to change notification settings - Fork 169
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
Minimal Python container to build az aro
extension
#3439
Minimal Python container to build az aro
extension
#3439
Conversation
b993ac4
to
5b64c4d
Compare
Please rebase pull request. |
b043347
to
0ea1d01
Compare
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I think we'd all prefer for the style/lint/etc to be included, I agree with your assessment that we can explore options in subsequent PRs since it seems like a lot of additional work. This is a great MVP for us to iterate on. Thanks Tanmay!
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
Please rebase pull request. |
/azp run e2e |
Pull request contains merge conflicts. |
Rebased and opened replacement PR w/ in-repo branch for CI checks: #3490 |
Which issue this PR addresses:
Small step for ARO-5088
What this PR does / why we need it:
az aro
extension with no other dependenciesTest plan for issue:
Manually invoke target and ensure it creates an
aro-${VERSION}-py2.py3-none-any.whl
file within./python/az/aro/dist
.Is there any documentation that needs to be updated for this PR?
Eventually, https://msazure.visualstudio.com/AzureRedHatOpenShift/_wiki/wikis/ARO.wiki/188187/AzureCLI-preview-extension-publishing# should be updated to include this target.
Additional Notes
azdev
command (style
/linter
/test
).azdev
requires that it be run within the context of a Git repository, as well as from within a specific virtualenv.