You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently username is passed through pipeline.yml as plugin input or read from agent hook if env for username set as "BUILDKITE_PLUGIN_DOCKER_LOGIN_USERNAME". It is not interpolated if it is set as an env via pipeline or post-checkout hook etc.
Since we are already passing the username in the pipeline.yml can we consider reading it from pipeline env or repo hook etc?
The text was updated successfully, but these errors were encountered:
Instead of using the username plugin option, couldn't the pipeline or hook set the variable BUILDKITE_PLUGIN_DOCKER_LOGIN_USERNAME directly? I don't see why that wouldn't work
@toote just removing username from plugin option works if we pass the env BUILDKITE_PLUGIN_DOCKER_LOGIN_USERNAME from pipeline directly or set via post-checkout.
It seems the other usecase is to pass org specific env var to username in the plugin, this would need plugin username to accept env variable which could be anything.
Currently username is passed through pipeline.yml as plugin input or read from agent hook if env for username set as "BUILDKITE_PLUGIN_DOCKER_LOGIN_USERNAME". It is not interpolated if it is set as an env via pipeline or post-checkout hook etc.
Since we are already passing the username in the pipeline.yml can we consider reading it from pipeline env or repo hook etc?
The text was updated successfully, but these errors were encountered: