Propagate environment details to dedicated instances in order to ease troubleshootings - Githubissues

orange-cloudfoundry / cf-ops-automation-broker

On demand dedicated services through COA concourse pipeline engine

4 stars 0 forks source link

Propagate environment details to dedicated instances in order to ease troubleshootings #237

Open gberche-orange opened 4 years ago

gberche-orange commented 4 years ago

As a paas-templates operator,
in order to troubleshoot dedicated COAB instances
I need dedicated instances to include details about
- the coab broker version that generated the dedicated instance secret/templates
- the version of paas-templates artefacts including
  - the common broker scripts that executes associated broker push and smoke tests

Alternative locations for such details:

in the git commit message
in the git tree in the coab-vars.yml. This could potentially enable propagating this downstream to dedicated instances resources such as vm tags

/cc @poblin-orange

gberche-orange commented 4 years ago

Paas-templates version can be injected to coab broker as an environment variable
COAB jar version is in the jar in a meta-inf file