-
Notifications
You must be signed in to change notification settings - Fork 47
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
Ability to directly specify the auth token #72
Comments
Hi @jemerald, |
I have thought about that, however it has 2 problems:
We are current using this workaround: def kubeConfig = readYaml file: env.KUBECONFIG
kubeConfig.users[0].user.token = authToken
writeYaml file: env.KUBECONFIG, data: kubeConfig, overwrite: true However this workaround is still a little coupled to the structure of the config file. Will you consider adding support for passing in the token to |
Agreed
The purpose of this plugin is to help configure |
Currently the
withKubeConfig
function only accepts JenkinscredentialsId
, but our company requires actual user's token when deploying to production (as a mean to restrict the users that can deploy to production).So out pipeline would prompt the user to enter his token before deploying to production.
Is it possible to add an extra parameter in the plugin to allow passing in the token directly?
The text was updated successfully, but these errors were encountered: