Keep PipelineResource.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 tektoncd#1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
vdemeester · Dec 19, 2019 · 5bb50ee · 5bb50ee
1 parent de5493e
commit 5bb50ee
Show file tree

Hide file tree

Showing 2 changed files with 33 additions and 0 deletions.
diff --git a/pkg/apis/pipeline/v1alpha1/resource_types.go b/pkg/apis/pipeline/v1alpha1/resource_types.go
@@ -163,6 +163,18 @@ type PipelineResource struct {
 
 	// Spec holds the desired state of the PipelineResource from the client
 	Spec PipelineResourceSpec `json:"spec,omitempty"`
+
+	// Status is deprecated.
+	// It usually is used to communicate the observed state of the PipelineResource from
+	// the controller, but was unused as there is no controller for PipelineResource.
+	// +optional
+	Status *PipelineResourceStatus `json:"status,omitempty"`
+}
+
+// PipelineResourceStatus does not contain anything because PipelineResources on their own
+// do not have a status
+// Deprecated
+type PipelineResourceStatus struct {
 }
 
 // PipelineResourceBinding connects a reference to an instance of a PipelineResource

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