Skip to content

Update fields in the spec to no longer be a pointer #1146

@everettraven

Description

@everettraven

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:

Metadata

Metadata

Labels

epic/v1-apigood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.v1.0Issues related to the initial stable release of OLMv1

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions