• sharing templates between multiple Helmfiles in different repos, and
• sharing a default set of releases with dependencies between eachother, and
• retaining the ability to override/change one or more of those releases (i.e. no sub-helmfile usage, since sub-helmfiles don’t get exposed to their parent) ?
All I could come up with so far is this, which seems a bit hacky:
Are there any articles of best practices on how to deal with timed out waiting for condition errors I would be amazing to at least have a message that displays when that error occurs to point application engineering on the right direction