Ricardo Amaro

Oh, I misunderstood you. Right now you can run `kapitan compile --reveal` at the stage where it makes sense to have revealed artefacts. Let me know if that works for...

Yes that is a valid point. Compiling again is not ideal and the ref reveal command could offer such functionality, but it's a decent workaround. I will leave this open...

Will this change work when compiling a ref in a template that is not set in the inventory? e.g. ```json { "secret_key": "?{gkms:secret/value}", } ```

@eug-maly curious to know why you have a dependency on the order of compilation? You can always iterate through compiled target names and match/order externally. Alternatively, you should consider @AlphaRoy14...

@jperville thanks for reporting! Definitely related to #621

@jperville to confirm, are you setting the inventory's `dependencies.type` to `helm` or or `http(s)/git`?

These have now been fixed https://github.com/google/go-jsonnet/issues/322 https://github.com/google/go-jsonnet/issues/323

@alldroll ctypes should work just fine - however the second approach is ideal, in which case, I agree that that it makes sense to add it to `go-jsonnet`

Progress is being made and some bugs and issues are being found along the way. Unfortunately at the moment I don't have a fully working version of it yet. On...

Hey @xunleii great to hear you're using Kapitan! > After some research, I deduce that these "deadlocks" are due to the way python handles multiprocessing by using fork. These "locks"...