Sorry for the slow reply here!
- The helm template in the chart doesn’t exist at all in the chart, so I want to add it. I think you covered this above with the ship.yaml
Yeah, this sounds like it can be covered by adding files, which ship’ll do fine.
- The helm template in the chart exists, but it isn’t what we need, so we want to override it with a custom template. Often this might be something you are testing out before submitting a patch to the upstream chart or maybe a change to the chart that won’t be upstreamed because it is bespoke… but it requires the template logic and not just a simple kustomize override.
There’s a couple things to break down here. First off - if you have a branch with the patch on it, ship can refer to that branch just fine. That might work for testing there.
For bespoke changes requiring logic and overriding existing helm template logic, ship isn’t really set up for that . That being said, if you can formulate your changes as a set of dynamically generated kustomize patches, you should be able to programmatically render them with the use of golang templates and our config page. It would add an extra layer of configuration (helm values file + ship config screen) but that’s the best I can think of right now.