Bug 1794580

Summary:	spec.customresourcedefinitions.owned.specDescriptors.value type string vs RawJSON
Product:	OpenShift Container Platform	Reporter:	Matt Dorn <mdorn>
Component:	OLM	Assignee:	Evan Cordell <ecordell>
OLM sub component:	OLM	QA Contact:	Jian Zhang <jiazha>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	bsong
Version:	4.4
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-28 17:14:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1794484, 1794553

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