dev-branch-deploy

# Dev-Branch Deploy — Hermes & Maia Test a Hermes or Maia stack change in a **live lab region before merging to master**, using the pipeline's parallel `dev` lane. One workflow, two stacks — parametrized by stack. ## The problem this solves Concourse pins a git `branch:` per resource at pipeline-definition time; you can't override it at trigger time. So normally you must merge to `master` to see a chart/secrets change run in a lab. The `dev` lane adds a second set of jobs pointed at `<stack>-dev-branch`, so you deploy and validate in a real lab region with **no risk to master or production**. ## Stack parameters Everything below is identical between stacks except these values. | Param | hermes | maia | |-------|--------|------| | Dev branch | `hermes-dev-branch` | `maia-dev-branch` | | fly target | `ci-monitoring` | `monitoring` | | Concourse | `https://ci1.eu-de-2.cloud.sap` | `https://ci.eu-de-2.cloud.sap` | | Pipeline dir | `ci/hermes/` in `cc/secrets` | `ci/maia/` in `cc/secrets` | | `set-pipeline` vars | — | `--load-vars-from vars.yaml` | | Chart | `openstack/hermes` | `openstack/maia` | **Constants (both stacks):** - Team: `monitoring` - Lab regions the dev lane deploys to: `qa-de-1`, `qa-de-2`, `qa-de-3`, `eu-de-3` - Repos the dev branch must exist on: `cc/secrets` (GHE `github.wdf.sap.corp`) **and** `sapcc/helm-charts` (github.com) - Local `cc/secrets` clone: `~/gh/secrets` ## The two lanes | Lane | Branch | Role | |------|--------|------| | `labs` | `master`...