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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(pipelines): step outputs #19024
feat(pipelines): step outputs #19024
Changes from 9 commits
9b0efeb
7976dbe
6823efb
be327a2
26c5dad
17538b9
1fad359
fbdf7ca
b062225
2b4cf40
e6d2440
176503d
dd0f083
cd78286
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like and/or don't understand this naming convention. I get that it is engine specific, but I don't see the need to call this out in the name and make it so cryptic. We are sending in the
variableName
in codepipeline, what other values are you imagining could be sent in here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Depends on the engine.
For CodePipeline, it happens to be the variable name. But I suppose I can rename it. Let's talk later today.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused why we are sending
variableName
as the value forengineSpecificInformation
toStepOutput
. It doesn't seem like the variable name is engine specific. Feels likeengineSpecificInformation
could be named better.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea about "engineSpeicificInformation" is that it is arbitrary information that doesn't matter to the framework.
It matters to the engine, and only the engine gets to interpret it.
In this case, for the CodePipeline engine, the only thing necessary is the variable name (as the step itself is already known).
I suppose I could make it just a string, and if the engine needs to encode something else into it, it can just JSON-encode something in there...?