[CLOUD-728] Wrong azure CLI parameter in the documentation when creat…

…ing the role assignment (#387)
logicalclocks · May 24, 2024 · 3829955 · 3829955
1 parent a4cae5c
commit 3829955
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/setup_installation/azure/aks_acr_integration.md b/docs/setup_installation/azure/aks_acr_integration.md
@@ -26,13 +26,13 @@ aksidentity=$(az aks create --resource-group $RESOURCE_GROUP --name hopsworks-ak
 You need to add permission to [the managed identity you will assign to your Hopsworks cluster](getting_started.md#step-4-create-a-managed-identity) to access the AKS cluster. To do it run the following command, replacing *\$RESOURCE_GROUP* with the resource group in which you will run your cluster and $identityId with the *id* of the identity you will assign to your Hopsworks cluster.
 
 ```bash
-az role assignment create --resource-group $RESOURCE_GROUP --role "Azure Kubernetes Service Cluster User Role" --assignee $identityId
+az role assignment create --scope /subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP --role "Azure Kubernetes Service Cluster User Role" --assignee $identityId
 ```
 
 You also need to grant permission to pull images from the [ACR](getting_started.md#step-3-create-an-acr-container-registry) to the AKS nodes. To do it run the following command, replacing *\$RESOURCE_GROUP* with the resource group in which you will run your cluster
 
 ```bash
-az role assignment create --resource-group $RESOURCE_GROUP --role "AcrPull" --assignee $aksidentity
+az role assignment create --scope /subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP --role "AcrPull" --assignee $aksidentity
 ```
 
 

diff --git a/docs/setup_installation/azure/getting_started.md b/docs/setup_installation/azure/getting_started.md
@@ -170,7 +170,7 @@ az role definition create --role-definition instance-role.json
 Finally assign the role to the managed identity by running the following command, replacing *$RESOURCE_GROUP* with the name of your resource group.
 
 ```bash
-az role assignment create --resource-group $RESOURCE_GROUP --role hopsworks-instance --assignee $identityId
+az role assignment create --scope /subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP --role hopsworks-instance --assignee $identityId
 ```
 
 !!!note
-Original file line number
+Diff line change
@@ Expand Up @@
     Finally assign the role to the managed identity by running the following command, replacing *$RESOURCE_GROUP* with the name of your resource group.
     ```bash
-    az role assignment create --resource-group $RESOURCE_GROUP --role hopsworks-instance --assignee $identityId
+    az role assignment create --scope /subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP --role hopsworks-instance --assignee $identityId
     ```
     !!!note
@@ Expand Down @@