chore: documentation adjustment

hands-on-lab/HOL step-by-step - DevSquad in a Day.md

@@ -443,35 +443,6 @@ The CD pipeline will be triggered automatically after the CI Pipeline. After exe
 
 >**Note**: Name of the Resource Groups and Resources depends on the custom alias defined by yourself and also the suscription id.
 
-With these resources created, you can configure a secrets scope in databricks, for secure management of secrets.
-
-##### **Databricks Secrets Scope**
-
-When you have the resources created in the environment, it is time to configure the scope secrets in databricks, to do that, run the PowerShell script located at `infrastructure-as-code/scripts` to create the Databricks secrets scope for **each environment**:
-
->**Note**: To get `$clientSecret` it is necessary to create a second client secret in the services principal (the first was used in the service connection configuration in the project in DevOps), it could be used for all environments.
-
-![](./media/SP-secret.PNG)
-
->**Note**: Remember copy the value because only is showen one time.
-
-![](./media/copy-value-clientsecret.PNG)
-
-Now, you should to change some parameters with your information and execute this script, and how the resources in development environment were created then we can create the scope in databricks dev.
-
-```
-$clientSecret = ConvertTo-SecureString -AsPlainText
-
-./DatabricksSecrets.ps1 `
-    -ClientID "<client_id>" `
-    -ClientSecret $clientSecret `
-    -DataResourceGroup "<data_resource_group_name>" `
-    -ComputeResourceGroup "<compute_resource_group_name>" `
-    -KeyVaultName "<kv_name>" `
-    -DataLakeName "<adls_name>" `
-    -DatabricksName "<databricks_name>"
-```
-
 >**Note**: To see Key names in secret scope dataops execute the follow command.
 
 ```

hands-on-lab/archival/HOL Exercise 3.md

@@ -159,35 +159,7 @@
     ![](./media/RGDataDev.PNG)
 
     >**Note**: Name of the Resource Groups and Resources depends of the alias and the suscription id.
-
-    With this resources created, you can configure the scope in databricks.
-
-    ## Databricks Secrets Scope
-
-    When you have the resources created in the environment, it is time to configure the scope secrets in databricks, to do that, run the PowerShell script located at `infrastructure-as-code/scripts` to create the Databricks secrets scope for **each environment**:
-
-    >**Note**: To get `$clientSecret` it is necessary to create a second client secret in the services principal (the first was used in the service connection configuration in the project in DevOps), it could be used for all environments.
-
-    ![](./media/SP-secret.PNG)
-
-    >**Note**: Remember copy the value because only is showen one time.
-
-    ![](./media/copy-value-clientsecret.PNG)
-
-    Now, you should to change some parameters with your information and execute this script, and how the resources in development environment were created then we can create the scope in databricks dev.
-
-    ```
-    $clientSecret = ConvertTo-SecureString -AsPlainText
-
-    ./DatabricksSecrets.ps1 `
-      -ClientID "<client_id>" `
-      -ClientSecret $clientSecret `
-      -DataResourceGroup "<data_resource_group_name>" `
-      -ComputeResourceGroup "<compute_resource_group_name>" `
-      -KeyVaultName "<kv_name>" `
-      -DataLakeName "<adls_name>" `
-      -DatabricksName "<databricks_name>"
-    ```
+    
     >**Note**: To see Key names in secret scope dataops execute the follow command.
 
     ```