Skip to content
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

Merged
merged 2 commits into from
Apr 16, 2024

Conversation

ashwinmayya
Copy link
Member

@ashwinmayya ashwinmayya commented Apr 11, 2024

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

  • 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.

Copy link

azure-client-tools-bot-prd bot commented Apr 11, 2024

️✔️Azure CLI Extensions Breaking Change Test
️✔️Non Breaking Changes

Copy link

Hi @ashwinmayya,
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 Apr 11, 2024

quantum

Copy link

⚠️ Release Suggestions

Module: quantum

  • Update version to 1.0.0b3 in setup.py

Notes

  • Stable/preview tag is inherited from last release. If needed, please add stable/preview label to modify it.
  • Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add major/minor/patch/pre label to adjust it.
  • For more info about extension versioning, please refer to Extension version schema

Copy link
Contributor

@kikomiss kikomiss left a comment

Choose a reason for hiding this comment

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

LGTM

@jsntcy
Copy link
Member

jsntcy commented Apr 12, 2024

Do we have any tests to cover this change?

@ashwinmayya
Copy link
Member Author

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.

@ashwinmayya ashwinmayya reopened this Apr 15, 2024
@kairu-ms kairu-ms merged commit e6fbe08 into Azure:main Apr 16, 2024
15 checks passed
@azclibot
Copy link
Collaborator

[Release] Update index.json for extension [ quantum ] : https://dev.azure.com/azclitools/release/_build/results?buildId=149062&view=results

blackchoey pushed a commit to blackchoey/azure-cli-extensions that referenced this pull request Apr 29, 2024
…linked StorageAccount (Azure#7497)

* Assign storage account contributor to workspace

* Update version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot Quantum az quantum
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants