CI-14277:add support for base64 encoded env secret docker secrets #40
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Aishwarya-Lad
force-pushed
the
CI-14277
branch
from
ba12776 to
ab26063
Compare
Ompragash
approved these changes
Oct 23, 2024
Aishwarya-Lad
force-pushed
the
CI-14277
branch
from
7571b6d to
2aa1844
Compare
This was referenced Oct 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Allow docker secrets via environment var and harness secret types to be used in buildx plugin at build time.
Testing: Dockerfile shows docker secret via env (docker_user) and harness_secret (docker_pass) to be used in a docker login command at run-time.
Output console shows build command and output of the docker run