-
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
Refactor Pipeline Parameters Validation #3167
Refactor Pipeline Parameters Validation #3167
Conversation
Currently, pipeline parameters are only used in task parameters. we need to use Pipeline Parameters in When Expressions as well. Trying to add the new validation became ugly, so we're refactoring parameters validation so ' that we can easily add validation for parameters in when expressions.
The following is the coverage report on the affected files.
|
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.
Nice!! Thanks for breaking this out. I think this is a lot clearer as several larger functions than the one line wrapper functions we had before
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bobcatfish 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 |
/test check-pr-has-kind-label |
/test check-pr-has-kind-label |
Changes
Pipeline parameters were previously only used in task parameters. We need to use pipeline parameters in when expressions.
We're refactoring pipeline parameters validation so that we can easily add validation for parameters in when expressions.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
/cc @bobcatfish @pritidesai