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.

Sign up for GitHub

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

Jump to bottom

blob(chore): add missing instruction #1953

Merged
merged 1 commit into from
Mar 19, 2024
Merged

blob(chore): add missing instruction #1953

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/dev/features/object-storage/blobcsi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -265,6 +265,10 @@ Follow the steps below to create the necessary secrets in the Azure Portal, then
8. Send the Application (client) ID to the appropriate JIRA page.
9. Add the secret to the Gitlab CI/CD settings.

### 4. Update the `EntraID group`
As seen in this [jira ticket](https://jirab.statcan.ca/browse/CODAS-2402?focusedId=1530401&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1530401) you will need to add the newly created SP to the relevant group, as without it the user would not be able to view the Storage Account listed from their AVD.
Example) for the `aaw-agzero-unclassified-prod-sp` I had to add it as a member under the `AAW-PROD-External-Unclassified-SPs` entraID group

# Architecture Design

For more context on the blob-csi system as a whole (from deployment of infrastructure to azure containers), see the attached diagram below.
Expand Down
Loading