Repository navigation
[enhancement] add configuration schema to the StateManagementProvider #2234
Description
Activity
I have the following discussion points:
- This could be useful to check for config fields for the provider but users can also check the CRD for the object.
- I think this would increase maintenance for the StateManagement Provider authors because the underlying provider should already perform validation when a misconfigured object is created.
- This could be useful to check for config fields for the provider but users can also check the CRD for the object.
No,
StateManagementProviderdoes not contain provider-specific config options. AndserviceSpec.provider.configis anapiextv1.JSONfield. So, it's not possible to just check the CRD.- I think this would increase maintenance for the StateManagement Provider authors because the underlying provider should already perform validation when a misconfigured object is created.
It could be optional, so that if user won't increase complexity of the
StateManagementProviderobject it won't. However, if such a schema is added, then user could implement validation in its custom controller.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
I assume it could be useful to be able to validate provider's configuration set in .spec.serviceSpec.provider.config using some predefined schema.
I assume that the StateManagement provider could host this schema and the ServiceSet controller could use it to validate provided configuration before converting it to the provider-specific object.
Benefits: