xaniasd
xaniasd
kfctl set-image-name command appends inventory:omitempty: null into all the kustomization.yaml files
@hemantha-kumara doesn't sound like expected behaviour. I can't find quickly the code doing this, I'll try to reproduce the issue and get back to you.
kfctl set-image-name command appends inventory:omitempty: null into all the kustomization.yaml files
Found it. There's a bug in kustomization v3.1.0 [here](https://github.com/kubernetes-sigs/kustomize/blob/v3.1.0/pkg/types/kustomization.go#L142) is the offending code.
kfctl set-image-name command appends inventory:omitempty: null into all the kustomization.yaml files
sure thing!
Hi @lilatomic, thanks for the response. Thanks for putting some (needed) work on the terraform backend, even without the docs :) On the overall approach, doesn't marking a module as...
Sort of. We have one repo that holds the terraform modules and another that generates tfvars for these modules, we basically generate instances of the "root" modules dynamically. So development...
as far as my limited knowledge of pants internals goes, it looks good to me! Thanks for the quick fix. btw, it is often useful to determine the order root...
I've seen those issues, but no conclusive decision yet. I guess my point is that this one is an easy fix ;-) keep up the good work!
I see. How about making it optional but defaulting to run unless explicitly configured not to? I'm using Unicorn. If there's something I can check for you with my set-up,...
they are external to the options block. I will create a PR and hope your backlog gets smaller soon :) see: http://www.zytrax.com/books/dns/ch7/controls.html thanks!