stefanprodan/kustomizer

Allow overriding the path to the config file

Opened this issue · 0 comments

Hi, I have a use case where I have some custom resources in my manifest, and ideally they need to be created in a specific order, I can solve this by listing them in the config file - yeah thanks for this feature. - however, I really want to commit this config to git along with the manifests and build scripts etc.

It appears that the config file path is hardcoded to $HOME/.kustomizer/config, so to do this I would have to add a step to my build script to copy the config file to that location (and hope we never have 2 different versions that run at the same time)

Can we have a command line parameter that sets the location of the file that we will loaded (like --kubeconfig to kubectl), or if you really don't want that an environment variable to override the default name (like $KUBECONFIG does for kubectl), or both :-) .

Many thanks for considering this.