[ENHANCE] Provide options in helmify CLI to set up chart dependencies in generated chart.yaml

[MuneebAijaz]

Hi, we have recently started exploring Helmify for internal work, and found Helmify great when fix issues with inconsistencies between config folder for operators and hand-written helm chart.

We however do have usecases where we would like Helmify to also pick up chart dependencies and add it in Chart.yaml when creating it. The reason we dont want to maintain Chart.yaml separately is to avoid manual changes and keep one source of truth for our operator which would be kustomize manifests under config folder.

The idea is to define options in helmify cli for it to pick up dependency charts and add it to chart.yaml (even better if it also take default values.yaml from dependency charts and add it under parent values.yaml file). If cli options feels like too much complexity to handle multiple dependency charts, another idea could be to parse a configuration file for Helmify to read and understand.

Open to discuss and alternatives if they fix the same problem.

[arttor]

good idea.

what do you think about implementation? should it be more generic?

For example, add the following options:

$ helmify --chart-merge ./dependencies.yaml --values-merge ./dependencies-values.yaml


$ cat ./dependencies.yaml
dependencies:
  - name: redis
    version: 17.11.3
    repository: https://charts.bitnami.com/bitnami
    condition: redis.enabled


$ cat ./dependencies-values.yaml
redis:
  enabled: true
  architecture: standalone

Here, helmify will read provided yamls and merge content of dependencies.yaml into Chart.yaml and dependencies-values.yaml into values.yaml.

[MuneebAijaz]

yes makes perfect sense, --chart-merge can also allow us to add other fields, like icon, source, keywords, and maintainers.