Keep Pipeline.status field for backward compatibility 👾

They are not used, and shouldn't be there, but client that have previous version of this struct would fail targeting the API. This is a *partial* revert of #1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
tektoncd · Dec 18, 2019 · 5e2f899 · 5e2f899
1 parent cf8705b
commit 5e2f899
Show file tree

Hide file tree

Showing 2 changed files with 34 additions and 0 deletions.
diff --git a/pkg/apis/pipeline/v1alpha1/pipeline_types.go b/pkg/apis/pipeline/v1alpha1/pipeline_types.go
@@ -59,6 +59,19 @@ type Pipeline struct {
 	// Spec holds the desired state of the Pipeline from the client
 	// +optional
 	Spec PipelineSpec `json:"spec"`
+
+	// Status is deprecated.
+	// It usually is used to communicate the observed state of the Pipeline from
+	// the controller, but was unused as there is no controller for Pipeline.
+	// +optional
+	Status *PipelineStatus `json:"status,omitempty"`
+}
+
+// PipelineStatus does not contain anything because Pipelines on their own
+// do not have a status, they just hold data which is later used by a
+// PipelineRun.
+// Deprecated
+type PipelineStatus struct {
 }
 
 func (p *Pipeline) PipelineMetadata() metav1.ObjectMeta {

diff --git a/pkg/apis/pipeline/v1alpha1/zz_generated.deepcopy.go b/pkg/apis/pipeline/v1alpha1/zz_generated.deepcopy.go