-
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
Parameters should default to type string #5175
Comments
/assign @Yongxuanzhang |
@jerop: GitHub didn't allow me to assign the following users: Yongxuanzhang. Note that only tektoncd members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
/assign |
For what it's worth, I would suggest we add a commit on the release-v0.37.x branch adding types to |
@jerop Ok, now you shouldn't actually need to worry about changing |
So can we close this issue? Very glad that we can find out the reason eventually. 😄 |
We still need the validation/defaulting/etc to kick in for unchanged |
Could you elaborate more on unchanged Pipelines and Tasks? We're planing to add SetDefaults to reconcile so even without mutating webhook, we can also add missing values. Does this solution sounds good to you? |
Right, that's exactly what I mean. I'm just saying this issue shouldn't be closed until #5176 merges. |
Yeah sure! Np! |
Yes, we do. But the type defaulting behavior is not new and has been around for more than a release. So I don't think this issue needs to block the release |
I think this can be closed now right @Yongxuanzhang @abayer ? |
Yeah I think so. |
Agreed |
Expected Behavior
Pipelines
withParameters
that have no"type"
specified work with the default value of"string"
.Actual Behavior
Pipelines
withParameters
that have no"type"
fail.Example failures in dogfooding are here: https://dashboard.dogfooding.tekton.dev/#/namespaces/default/pipelineruns
Steps to Reproduce the Problem
Pipeline
with aParameter
without a default value specified.Pipeline
PipelineRun
logs.Additional Info
Ran into this error when running the release
Pipeline
which uses the default types forParameters
- https://github.com/tektoncd/pipeline/blob/94055d92c120a6010f3d61a821e45dea4f893a74/tekton/release-pipeline.yamlThis was also observed in other
Pipelines
in dogfooding - tektoncd/plumbing#1148A related issue with
types
inResults
was fixed in #5043 and patched in release v0.37.1Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
cc @Yongxuanzhang @chuangw6 @lbernick @dibyom @afrittoli @abayer
The text was updated successfully, but these errors were encountered: