How to Deploy Vault-injector

Modify Caascad Zones

Create a new branch within caascad-zones.

Edit zones.cue and add features: vault_injector: true to each target zone. Ex:

prdgso: {
                parent_zone_name: "ocb-esagso"
                provider:         #ProviderFE & {
                        domain: name: "OCB0005426"
                }
                features: vault_injector: true
        }

A new zones file should be compiled following the instructions in the caascad-zones README. All changes should be pushed to gitlab and merged into the master branch using a merge request.

A "robot" will create a second MR in envs-ng with the changes required for trackbone to use the new caascad-zones file. Should this automatic step fail, proceed with the next step.

If a new MR shows up in the envs-ng repository, use our change management procedures to apply the changes (review and validate MR, CAASCHR etc).

Optional: When the Robot Fails to Create a MR in envs-ng

Trackbone's nix sources have to be modified such that they point to the latest version of caascad-zones. This is done in the envs-ng repository:

git pull
nix-shell
$ niv update zones -a branch=master
Update zones
Done: Update zones

The nix/sources.json file should show some changes:

$ git diff nix/sources.json
diff --git a/nix/sources.json b/nix/sources.json
index c09cf120..bf7b04b7 100644
--- a/nix/sources.json
+++ b/nix/sources.json
@@ -9,7 +9,7 @@
     "zones": {
         "branch": "master",
         "repo": "https://git.corp.caascad.com/caascad/caascad-zones",
-        "rev": "cebfe3855cf47dc82fbbe095fbbf560367274509",
+        "rev": "e296b04fb60483a10f0f9fc0bf84ad669b00fa2b",
         "type": "git"
     }
 }

The modifications should be merged into the envs-ng master branch using the normal change management procedures (MR, CAASCHR etc).