Skip to content
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

Implicit params: only propagate params to embedded TaskSpecs in Pipelines. #4484

Merged
merged 1 commit into from
Jan 21, 2022

Conversation

wlynch
Copy link
Member

@wlynch wlynch commented Jan 13, 2022

Changes

Previously we were appling the params to all PipelineTasks, including
refs. This is incorrect behavior since the parameters should only be
propagated to things within the same document.

Fixes #4483

/kind bug

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes

[alpha only] Fixes bug where implicit params were erroneously passed to TaskRefs within ParamSpecs.

Previously we were applying the params to all PipelineTasks, including
refs. This is incorrect behavior since the parameters should only be
propagated to things within the same document.
@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/bug Categorizes issue or PR as related to a bug. labels Jan 13, 2022
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 13, 2022
@wlynch
Copy link
Member Author

wlynch commented Jan 13, 2022

/hold

(there's some additional discussion going on around this feature, so blocking submission for the time being)

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 13, 2022
@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/pipeline/v1beta1/pipeline_defaults.go 92.3% 100.0% 7.7

@wlynch
Copy link
Member Author

wlynch commented Jan 14, 2022

/test pull-tekton-pipeline-alpha-integration-tests

Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems good to me 👼🏼

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 14, 2022
@ghost ghost added this to the Pipelines v0.32 milestone Jan 19, 2022
@ghost ghost added the needs-cherry-pick Indicates a PR needs to be cherry-pick to a release branch label Jan 19, 2022
@pritidesai
Copy link
Member

thank you @wlynch
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2022
@wlynch
Copy link
Member Author

wlynch commented Jan 21, 2022

/hold cancel

@tekton-robot tekton-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2022
@tekton-robot tekton-robot merged commit ef5a83c into tektoncd:main Jan 21, 2022
@ghost ghost removed the needs-cherry-pick Indicates a PR needs to be cherry-pick to a release branch label Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implicit params being propogated to Refs
4 participants