Make COS configuration optional in runtime configurations #2337
Description
Is your feature request related to a problem? Please describe.
Runtime [environment] configurations currently include
- misc properties (name, description, tags)
- runtime specific properties (shown for Kubeflow Pipelines below)
- cloud object storage properties
Currently a user must provide cloud object storage properties. With the introduction of custom components for runtime specific pipelines, the cloud object storage properties should no longer be considered required and a user have the ability to not specify any.
For example, if a user creates a pipeline that comprises only custom components, access to a preconfigured cloud object storage is not required because custom components do not use it.
Describe the solution you'd like
Update the runtime schema (and enhance the metadata manager to support this) to treat a set of properties as "optional". For example, in the mockup below:
- box checked: the constraints for each property in the COS category are enforced
- box unchecked: the COS properties are not displayed
In both cases the source code should have the ability to determine whether the COS properties are set or not, without having to query individual values (e.g. whether or not the endpoint is empty).
