fix: handle _json_key .dockerconfigjson data #339
Closed
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.
Overview
Auth
field of typeinterface { }
, because this way the program can handle a_json_key
if it is received under theauth
key of a.dockerconfigjson
._json_key
and another check, if a vault path is received upfront at theauth
key.auth
field, we can assume that a_json_key
has been passed.Fixes #81
Notes for reviewers
dockerconfigjson
secrets.