Add option to populate decrypted key-pairs to outputs #8
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
hoangnd25
approved these changes
Oct 6, 2025
runlevel5
force-pushed
the
populate-vars-to-gh-outputs
branch
2 times, most recently
from
370879e to
84a46d0
Compare
Bump ejsonkms to 0.2.8
runlevel5
force-pushed
the
populate-vars-to-gh-outputs
branch
from
84a46d0 to
380b44a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 feature can be very convenient in the scenario where the pipeline has many steps that set environment variables which could lead to some vars get overridden by mistakes. By leveraging GitHub outputs, we give users ability to explicit target exact variables.