refactor: add a check for username override key variable from api #263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a username override key to internal container registry login in a similar manner to how #132 allowed for the password to be overridden.
Given the following container-registries block, and wanting to change the username for the account defined from
robot$robotic
to something else, you can add a project or environment variable of the scopecontainer_registry
with the nameREGISTRY_my-harbor_USERNAME
and set it to whichever username it should be instead.With a verify script https://gist.github.com/shreddedbacon/892f8206282aed54c029ed1979b6fcb6