Andrei Kvapil

I can also append that glob-import can be really useful for yaml files, eg I want to define all my qbec applications in argocd. ``` import 'glob-import:../*/qbec.yaml' ``` I would...

Ah probably fixed, this constriction is quite well, [docs](https://qbec.io/reference/jsonnet-glob-importer/), thank you!: ```jsonnet local a = import 'glob-importstr:../*/qbec.yaml'; { [x]: std.native('parseYaml')(a[x]) for x in std.objectFields(a) } ```

Good news, I just found that ArgoCD support helm hooks natively. Thus it will just run `qbec show ` to generate YAML, and consider the output as the rendered Helm-chart....

Sure! Most of the examples can be found in helm [charts/stable](https://github.com/helm/charts/search?q=%22helm.sh%2Fhook%22&unscoped_q=%22helm.sh%2Fhook%22) 61 chart of 282 are using helm hooks: ``` ambassador anchore-engine ark atlantis burrow centrifugo cloudserver cockroachdb collabora-code consul...

I'm so sad that Kubernetes API does not allow to overwrite the Job manifests and execute the jobs according the changed hash of podTemplate for them, that's why all these...

@gotwarlost it seems all the needed code for hooks is already implemented in [gitops-engine](https://github.com/argoproj/gitops-engine) project: https://github.com/argoproj/gitops-engine/tree/master/pkg/sync/hook This project combines the best from [Argo CD](https://argoproj.github.io/argo-cd/) and [Flux CD](https://fluxcd.io/). Not sure, if...

But it is doing that for the initial default environment. Isn't it?

Please keep it simple for end user. Allowing users to cusomize main structure is cool idea, but current example is really fine for the beginners who have no much experience...

Maybe leave this hierarchy structure only for `init --with-example`? I think it is good compromise to solve that, and keep simplicity for beginners :)

+1 for this, nice example @Andor 👍