From 789794f533a936ed728668614913b1b199faf44c Mon Sep 17 00:00:00 2001 From: "Jose Manuel (Ito)" Date: Tue, 19 Mar 2024 15:36:49 -0400 Subject: [PATCH] blob(chore): add missing instruction --- docs/dev/features/object-storage/blobcsi.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/dev/features/object-storage/blobcsi.md b/docs/dev/features/object-storage/blobcsi.md index 321f49fd7..c7e5cce57 100644 --- a/docs/dev/features/object-storage/blobcsi.md +++ b/docs/dev/features/object-storage/blobcsi.md @@ -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.