You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✨ Update .spec.config unmarshalling to accept yaml and json inputs (#2266)
* Improve .spec.config unmarshallig
Signed-off-by: Per Goncalves da Silva <[email protected]>
* Update .spec.config api doc to ellucidate validation
Signed-off-by: Per Goncalves da Silva <[email protected]>
---------
Signed-off-by: Per Goncalves da Silva <[email protected]>
Co-authored-by: Per Goncalves da Silva <[email protected]>
Copy file name to clipboardExpand all lines: docs/api-reference/olmv1-api-reference.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -254,7 +254,7 @@ _Appears in:_
254
254
| Field | Description | Default | Validation |
255
255
| --- | --- | --- | --- |
256
256
|`configType`_[ClusterExtensionConfigType](#clusterextensionconfigtype)_| configType is a required reference to the type of configuration source.<br /><br />Allowed values are "Inline"<br /><br />When this field is set to "Inline", the cluster extension configuration is defined inline within the<br />ClusterExtension resource. || Enum: [Inline] <br />Required: \{\} <br /> |
257
-
|`inline`_[JSON](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#json-v1-apiextensions-k8s-io)_| inline contains JSON or YAML values specified directly in the<br />ClusterExtension.<br /><br />inline must be set if configType is 'Inline'. || Type: object <br /> |
257
+
|`inline`_[JSON](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#json-v1-apiextensions-k8s-io)_| inline contains JSON or YAML values specified directly in the<br />ClusterExtension.<br /><br />inline must be set if configType is 'Inline'.<br />inline accepts arbitrary JSON/YAML objects.<br />inline is validation at runtime against the schema provided by the bundle if a schema is provided.|| Type: object <br /> |
258
258
259
259
260
260
#### ClusterExtensionConfigType
@@ -343,7 +343,7 @@ _Appears in:_
343
343
|`serviceAccount`_[ServiceAccountReference](#serviceaccountreference)_| serviceAccount is a reference to a ServiceAccount used to perform all interactions<br />with the cluster that are required to manage the extension.<br />The ServiceAccount must be configured with the necessary permissions to perform these interactions.<br />The ServiceAccount must exist in the namespace referenced in the spec.<br />serviceAccount is required. || Required: \{\} <br /> |
344
344
|`source`_[SourceConfig](#sourceconfig)_| source is a required field which selects the installation source of content<br />for this ClusterExtension. Selection is performed by setting the sourceType.<br /><br />Catalog is currently the only implemented sourceType, and setting the<br />sourcetype to "Catalog" requires the catalog field to also be defined.<br /><br />Below is a minimal example of a source definition (in yaml):<br /><br />source:<br /> sourceType: Catalog<br /> catalog:<br /> packageName: example-package || Required: \{\} <br /> |
345
345
|`install`_[ClusterExtensionInstallConfig](#clusterextensioninstallconfig)_| install is an optional field used to configure the installation options<br />for the ClusterExtension such as the pre-flight check configuration. |||
346
-
|`config`_[ClusterExtensionConfig](#clusterextensionconfig)_| config contains optional configuration values applied during rendering of the<br />ClusterExtension's manifests. Values can be specified inline.<br /><br />config is optional. When not specified, the default configuration of the resolved bundle will be used.<br /><br /><opcon:experimental>|||
346
+
|`config`_[ClusterExtensionConfig](#clusterextensionconfig)_| config is an optional field used to specify bundle specific configuration<br />used to configure the bundle. Configuration is bundle specific and a bundle may provide<br />a configuration schema. When not specified, the default configuration of the resolved bundle will be used.<br /><br />config is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide<br />a configuration schema the final manifests will be derived on a best-effort basis. More information on how<br />to configure the bundle should be found in its end-user documentation.<br /><br /><opcon:experimental>|||
expectedErrMessage: `invalid bundle configuration: error unmarshalling registry+v1 configuration: invalid value type for field "watchNamespace": expected "string" but got "object"`,
0 commit comments