Logically group fields in the spec #1148
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.
This change is unrelated to either the OpenShift or Kubernetes API Conventions and is focused on ensuring that fields are logically grouped and that these logical groupings are valid as our feature set and API is expanded post-v1.0.0.
Building on #1088 , the RFC proposed a structure similar to:
An example of a ClusterExtension, in YAML, with these changes (and building on top of the discriminated union changes):
Additionally, the
ClusterExtension.Status
should be updated to have logically grouped status information as well:Having these distinct, logical sections in both the
ClusterExtension.Spec
and theClusterExtension.Status
allows for logical expansion of fields. For example, if we wanted to add theClusterCatalog
that the bundle we resolved to was from in the status, it would be a straightforward update to add a new field to theResolutionStatus
struct above.The text was updated successfully, but these errors were encountered: