Monaco v2 env variables as part of the name

[Bert_VanderHeyd]

Hey guys,

I am trying out the new monaco v2 release candidate.

The convert works nice but I already found something unsupported.

V1 config ...

# Team BLUE
ao-team-blue-nonprod: 
  - name: "AO - Team - BLUE - {{ .Env.MONACO_ENVNAME  }}"
  - team: "BLUE"
  - env: "{{ .Env.MONACO_ENVNAME  }}"

V2 config ...

- id: ao-team-blue-nonprod
  config:
    name:
      name: MONACO_ENVNAME
      type: environment
    parameters:
      env:
        name: MONACO_ENVNAME
        type: environment
      team: BLUE
    template: ao-team-withenv.json
  type:
    api: alerting-profile

The "env" parameter is fine because the entire parameter comes from the environment variable Monaco_envname. However, the name should be a combination.  Like: "AO - Team - BLUE - {{ .Env.MONACO_ENVNAME }}"

Any ideas here, workaround.

[Bert_VanderHeyd · Accepted solution]

I found a possible solution. One of the supported types is called compound and looks exactly what I would need. https://www.dynatrace.com/support/help/manage/configuration-as-code/configuration/yaml-configuration...

Since we are using some configurations based on team and on environment I am now preprocessing (generating) the yaml files via powershell. Also a great way to avoid to much config.

[PedroDeodato]

Great solution, @Bert_VanderHeyd !

Started reading your original post and became quite scared, as I use "combinations" on names A LOT !!