Bug 1794580 - spec.customresourcedefinitions.owned.specDescriptors.value type string vs RawJSON
Summary: spec.customresourcedefinitions.owned.specDescriptors.value type string vs Raw...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.0
Assignee: Evan Cordell
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks: 1794484 1794553
TreeView+ depends on / blocked
 
Reported: 2020-01-23 21:12 UTC by Matt Dorn
Modified: 2020-01-28 17:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-28 17:14:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matt Dorn 2020-01-23 21:12:42 UTC 
Due to Structural Schema enforcement in OCP 4.4, users must now ensure values meet specified CRD types.

Do we know the intention behind setting spec.customresourcedefinitions.owned.specDescriptors.value as type RawJSON vs string? [1]

We see authors typically setting this as default value as "truth" or "false" string for ui:booleanSwitch. [2]

[1] https://github.com/operator-framework/operator-lifecycle-manager/blob/master/pkg/api/apis/operators/v1alpha1/clusterserviceversion_types.go#L94

[2] https://github.com/operator-framework/community-operators/blob/master/upstream-community-operators/couchbase-enterprise/1.2.1/couchbase-v1.2.1.clusterserviceversion.yaml#L111
Note You need to log in before you can comment on or make changes to this bug.