Skip to content

Application env specification should be a map, not list #705

Description

@filippomc

Currently the application environment can be specified as a list resembling the list on the kubernetes spec

application/myapp/values.yaml

harness:
  env:
    - name: A
      value: avalue
    - name: B
      value: bvalue   

The limitation of using a list is that values cannot be overridden in different environments, so if I want to change the A variable in values-dev.yaml I also have to specify B.

In order to make the change backwards compatible can add a new specification

harness:
  envmap:
     A: avalue
     B: bvalue   

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions