Sandbox Deployment

Automated Steps

Prerequisites

1. Access to the empower-clients repo
2. A light text editor such as VSCode will work perfectly

Steps

1. Pull empower-clients
2. Go to the file manifests/dv/sandbox-instances.yaml
3. Add to the yaml list under environments.
   1. name: This will be used to name the sandbox resource group and resources. Resource group name format will be {name}-empower-sandbox-southcentralus
   2. plan: If set to auto, this will keep the sandbox inline with the terraform deployment. Auto is good for initial deployment. Set to an empty string "" if manual customization is desired.
   3. empower_api_version: The version of the empower api to be deployed. Unless otherwise required, set to the latest stable version of the api.
4. Push up your changes and pr into development.
5. Once the new entry in the list is merged, automatic deployment should take 30 mins.

apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: sandbox
  namespace: empower-shared-services
spec:
  values:
    organizations:
      - name: sandbox
        environments:
          - name: test-helm # For testing sandbox deployments
            plan: "auto"
            empower_api_version: "x.x.x"

Manual Steps

Prerequisites

1. These must be done after the automated deployment.
2. You will need to be able to create managed identities in Hitachi's tenant
3. You will need access to the empower repo
4. You will need at least contributor on the sandbox resource group.

Steps

1. Complete the datafactory global parameters import process. Instructions

2. Complete the databricks secret scope setup. Instructions

3. Complete the one time mount point setup job. Instructions

4. Create three required folders in the datalake instructions

5. Copy keycloak-client-secret-neo-dv-df from augustus dv key vault and add it in the sandbox keyvault instructions

6. Create databricks access token and store it in the keyvault instructions