-
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
[quantum] Assign "Storage account contributor" role to workspace for linked StorageAccount #7497
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Hi @ashwinmayya, |
quantum |
|
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.
LGTM
Do we have any tests to cover this change? |
Yes these changes are covered by existing tests that create the workspace and submit jobs. There should be no change in functionality for existing users, hence no new tests. |
[Release] Update index.json for extension [ quantum ] : https://dev.azure.com/azclitools/release/_build/results?buildId=149062&view=results |
…linked StorageAccount (Azure#7497) * Assign storage account contributor to workspace * Update version
Previously, we assigned a contributor role to the storage account for the workspace. This PR changes it to the "storage account contributor" role. This is done in order to be compatible with the new "Quantum Workspace Owner" built-in role that allows constrained role assignment of storage account contributor.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)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
.