Update fields in the spec to no longer be a pointer #1146
Labels
epic/v1-api
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
v1.0
Issues related to the initial stable release of OLMv1
Milestone
Uh oh!
There was an error while loading. Please reload this page.
As outlined in the Pointers subsection of the OpenShift API Conventions, in configuration APIs, pointers should only be used when there is an explicit need to distinguish between a zero value and a nil value. An exception here is pointers in the Status subresource since a nil value has a different meaning in the Status subresource than the Spec.
We propose that the following fields, not having the explicit need to distinguish between the zero and nil values, should be updated to no longer be pointers:
The following fields do not have the explicit need to distinguish between the zero and nil values, meaning they should be updated to no longer be pointers based on the OpenShift API Conventions:
ClusterExtension.Spec.Preflight
:operator-controller/api/v1alpha1/clusterextension_types.go
Lines 84 to 85 in baac660
ClusterExtension.Spec.Preflight.CRDUpgradeSafety
:operator-controller/api/v1alpha1/clusterextension_types.go
Lines 103 to 105 in baac660
The text was updated successfully, but these errors were encountered: