Leveraging maven profiles

[gintautassulskus]

Have you considered the use of maven profiles for different deployment environments?

I came across this issue helm/helm#2620 that suggests storing common values in values.yaml and then overriding them with environment-specific values that are stored in an environment-specific file, e.g. prod-values.yml.

Would you consider an optionextraFiles that accepts a list of files with the overriding values?
Or, if possible, a generic, more flexible parameter extraOptions that passes a string to helm, e.g. -f prod-values.yml.

The process would look something like this:

1. In Maven pom.xml one would define profiles, e.g. dev, prod.
2. A chart folder would contain values.yaml, values-dev.yaml and values-prod.yaml for common, dev- and prod-specific values respectively.
3. Maven Helm plugin would be configured to pass the following string to helm:
   <extraOptions>-f values-${project.ActiveProfiles[0]}.yaml</extraOptions>

[ljnelson]

Hi; thanks for using the microBean Helm Maven Plugin.

First, to address a couple of things in here: this plugin does not work by invoking helm. So there's no -f option.

What you're suggesting is a simple matter of Maven profiles and configuration so in a limited sense is supported already.

The limitation that is the subject of another enhancement (#13) is that currently you can only supply values as a YAML string. Obviously it would be nice to allow you to supply them as a file or URI.