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

Parameter and Result Validation Schema #6615

Open
jerop opened this issue May 2, 2023 · 5 comments
Open

Parameter and Result Validation Schema #6615

jerop opened this issue May 2, 2023 · 5 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@jerop
Copy link
Member

jerop commented May 2, 2023

TEP-0075 had a long-term goal to support built in validation of Parameters and Results based on their schema:

Take a step in the direction of allowing Tasks to have even more control over their params and results (#1393) (e.g. one day providing built in validation for params as part of their declaration)

The schema validation will be useful for users with complicated types and restrictions for Parameters and Results. Here is an example and further description from @skaegi: #1393 (comment).

This issue is meant to track this work.

cc @bobcatfish

@jerop jerop added the kind/feature Categorizes issue or PR as related to a new feature. label May 2, 2023
@santhoshivan23
Copy link

@jerop I'd like to work on this.

@santhoshivan23
Copy link

/assign @santhoshivan23

@jerop
Copy link
Member Author

jerop commented May 8, 2023

Thank you @santhoshivan23! Let me know if I can help in any way 😀

@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 6, 2023
@jerop
Copy link
Member Author

jerop commented Aug 7, 2023

/lifecycle frozen

@tekton-robot tekton-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants