-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Migrate git-init image off PipelineResourceResult #6335
Migrate git-init image off PipelineResourceResult #6335
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e78dd84
to
9aa9414
Compare
/test pull-tekton-pipeline-integration-tests |
@@ -30,12 +30,12 @@ const ( | |||
) | |||
|
|||
// WriteMessage writes the results to the termination message path. | |||
func WriteMessage(path string, pro []v1beta1.PipelineResourceResult) error { | |||
func WriteMessage[T v1beta1.TaskRunResult | v1beta1.PipelineResourceResult](path string, pro []T) error { |
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.
This change doesn't require the changes to git-init; can this PR be focused just on just the changes to pkg/termination or at least wait until #6310 is merged? It could also tackle termination.ParseMessage
.
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.
Any reason to use generics here ? 🤔 Not that I am fundamentally against but…
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.
Oh because either TaskRunResult or PipelineResourceResult... 😓
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.
Oh because either TaskRunResult or PipelineResourceResult... 😓
trying to migrate off PipelineResourceResult while keeping it least confusing 😿 but seems it could also be confusing.
I will add more comments in the PR message/commit
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.
actually after trying out the unmarshall, i felt generics don't work well with unmarshalls
/hold |
This commit makes introduces the generics of PipelineResourceResult and TaskrunResult in termination package and migrates the git-init image off from using PipelineResourceResult.
9aa9414
to
95ddced
Compare
/hold cancel |
@JeromeJu do you know what the implications of swapping to a TaskRunResult are here? I think this may result in the git-init output being populated in a different part of the taskrun status and I'm not sure whether or not we want that |
addressed in #6417 |
Changes
This commit makes introduces the generics of PipelineResourceResult and TaskrunResult in termination package and migrates the git-init image off from using PipelineResourceResult.
/kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes