Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow overriding the path to the config file #91

Open
stocksr opened this issue Jan 26, 2024 · 0 comments
Open

Allow overriding the path to the config file #91

stocksr opened this issue Jan 26, 2024 · 0 comments

Comments

@stocksr
Copy link

stocksr commented Jan 26, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant