Add parsed_params output #322
Merged
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
Contributor
|
@fabn thank you for this! I can see a lot of value in having the parser / output controlled directly from this Action rather than having it be elsewhere. I will take some time to review and get these changed merged in for you. Thanks! |
GrantBirki
approved these changes
Nov 22, 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.
I need to pass some parameters to my deployment and I initially thought to write a simple action to parse parameters returned by this action. However the parser I chose and works out of the box with strings inputs returning a sensible set of defaults, so I sketched a simple params parser and integrated it into this action.
Let me know if you're interested in this so I can continue to develop this.