Conversation
|
Sorry for the delayed response, haven't been on github in a bit. The issue you're going to run into here, I think, is that every helm chart is different. For example:
Each key in a Helm chart is user-defined, so for example there's no such thing as mandatory fields. Builder would need to know more about the actual helm chart in order to be able to create a valid values file for that chart. It might be helpful to go through Helm's chart template guide to get a better sense of how Helm works and what might / might not be possible with a builder tool. I think one workflow that might work here would be to feed in one helm repo as context (assume it's in a github repo), and use that to then build out a structure (there's plugins that can help with this, like https://github.com/losisin/helm-values-schema-json). |
fixes #54
this is the first pass at creating the helm charts, and would like your guys opinions on what you think can be improved/if its ok. These agents would essentially be the backend of what the builder would use in the future.
I've decided with this approach, since I'm not too familiar with helm charts myself:
Step 1: HelmChart Template generator - Creates minimal templates w placeholder values
Step2: HelmValuesFiller - add values for specified fields and removes unnecssary ones
Step3: HelmValuesValidator - validate it is a valid schema