Inconsistency of Required v.s. Optional fields across docs. #5818
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
chuangw6
added a commit
to chuangw6/pipeline
that referenced
this issue
Nov 30, 2022
Fixes tektoncd#5818. Prior, `startTime` and `completionTime` are marked as optional fields in Run status, and `provenance` field was not marked as optional in Run status. Now, we remove `+optional` tag for `startTime` and `completionTime` in Run status, and add `+optional` tag for the `provenance` field. Signed-off-by: Chuang Wang <[email protected]>
7 tasks
Repository owner
moved this from Todo
to Done
in Tekton Community Roadmap
Dec 23, 2022
tekton-robot
pushed a commit
that referenced
this issue
Dec 23, 2022
Fixes #5818. Prior, `startTime` and `completionTime` are marked as optional fields in Run status, and `provenance` field was not marked as optional in Run status. Now, we remove `+optional` tag for `startTime` and `completionTime` in Run status, and add `+optional` tag for the `provenance` field. Signed-off-by: Chuang Wang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Required fields v.s. optional fields in PipelineRun status should be consistent across documentations.
Actual Behavior
docs/pipelinerun.md documents that
startTimeandcompletionTimeare required fields in PipelineRun status, but the docs/pipeline-api.md says those fields are optional.Steps to Reproduce the Problem
N/A
The text was updated successfully, but these errors were encountered: