-
Notifications
You must be signed in to change notification settings - Fork 14
feat: support params for pipelineruns and taskruns #23
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
base: main
Are you sure you want to change the base?
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 |
} | ||
|
||
paramStr := paramsArg[0] | ||
if paramStr == "" { |
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 think this check is not necessary, since you are checking the value again in ParsePipelineRunParams
function
value := kv[1] | ||
|
||
param, err := parseParamValue(key, value) | ||
if err != nil { |
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.
Is it wise to recreate parameter when there was an error during parsing?
paramDescs := make([]string, 0, len(pipelineParams)) | ||
for _, p := range pipelineParams { | ||
var valueStr string | ||
switch p.Value.Type { |
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 switch statement is the same one as in handlerStartTask function. Can it extract to a standalone function?
@@ -0,0 +1,71 @@ | |||
package tools |
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 would vote for introducing ginkgo testing framework (should not be part of this PR)
@waveywaves: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
Release Notes