-
Notifications
You must be signed in to change notification settings - Fork 139
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
Align 'Airlock Get Container URL' permissions with 'Create Airlock Request's permissions #3208
Align 'Airlock Get Container URL' permissions with 'Create Airlock Request's permissions #3208
Conversation
…y can also upload files to that request
…can create airlock requests
…7-align-airlock-get-container-url-permissions
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 :)
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/4125164688 (with refid (in response to this comment from @yuvalyaron) |
…7-align-airlock-get-container-url-permissions
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/4125836051 (with refid (in response to this comment from @yuvalyaron) |
Resolves #3187
What is being addressed
Verified that every role that is able to create an Airlock request is also able to upload a file to the request.
How is this addressed
Workspace Owner
to the roles that can access the container link when the status is notin_review