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

Emit warning or error for creation of v1 PipelineRun with "full" or "both" embedded status #5355

Closed
JeromeJu opened this issue Aug 23, 2022 · 5 comments

Comments

@JeromeJu
Copy link
Member

JeromeJu commented Aug 23, 2022

This issue tracks down the requirement of a similar validation function for the minimal Embedded Status for PipelineRun. Thanks to the discussion with @abayer and @lbernick , a warning should be emitted to users if they are creating a v1 PipelineRun while the feature flag is not set to "minimal".

However, right now in pipeline we don't have a great way of returning a warning to the user. Ideally we would want the webhook to accept the pipelinerun, but return a warning via its rest api.

Originally posted by and thanks to @lbernick in #5219 (comment)

@lbernick
Copy link
Member

#5373 would be useful here

@abayer
Copy link
Contributor

abayer commented Aug 25, 2022

So this wouldn't really be warning on a deprecated field, exactly - the Status.TaskRuns and Status.Runs fields are created/populated by the reconciler, not the CRD author. What could make sense would be checking if embedded-status isn't minimal during v1 PipelineRun creation and warning there...or maybe appending something to the PipelineRun.Status's Condition.Message saying "yeah, we don't support that?" in addition to whatever's already going there.

Actually, maybe the right answer is for v1 PipelineRun reconciliation to treat embedded-status being set to full as if it were set to both instead - populating both the deprecated Status.TaskRuns/Status.Runs and the new Status.ChildReferences.

@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 Nov 23, 2022
@vdemeester
Copy link
Member

/remove-lifecycle stale
I think we still need to discuss / handle this.

@tekton-robot tekton-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 29, 2022
@lbernick lbernick changed the title Required minimal EmbeddedStatus for v1 PipelineRun Emit warning or error for creation of v1 PipelineRun with "full" or "both" embedded status Nov 29, 2022
@lbernick
Copy link
Member

I think this issue is handled by #5813 so I'm going to close, feel free to reopen if needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

5 participants