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
Create Config without using auto-configure functionality or setting env variables #2319
Comments
@Fabian-K : Hi, extremely sorry for the late reply. I think you might already have figured it out yourself. I checked code and there seem to be property kubernetes-client/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/Config.java Lines 217 to 221 in c87dd30
|
No problem, thanks for the reply! Properties and Env Values are depending on the environment not always straight forward to set. I also somehow feel that it should be possible to say in code: "use exactly these config values which I provide". The no-argument constructor is deprecated for some time now (2017). What do you think about removing the autoConfigure part from it and simply return an empty config? This way, the ConfigBuilder would not include auto-configuration any more. To make the breaking change obvious, this could be a private constructor, used e.g. by a new static method Config.empty(). |
An alternative might be to offer a new static method |
We can do that, maybe by moving to 4.11.x and stress this in the release note. I don't think this is a change requiring a major bump like moving to 5.x |
…onality or setting env variables
…onality or setting env variables
…onality or setting env variables
…onality or setting env variables
Hi,
I´m looking for a away to create a Config without using auto-configuration functionality while not relying on env variables or properties.
Currently when constructing a config like this, it still invokes the auto-configuration. I instead want to explicitly use the values provided (as they differ in terms of authorization from what is provided via auto-configuration)
Is this already possible and I´m just not seeing it? :)
Thanks, Fabian
The text was updated successfully, but these errors were encountered: