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
Is your feature request related to a problem? Please describe.
Today, Elyra UI assumes all features are installed by default, including all different supported runtimes. When considering a real production deployment scenario, this might not be true, and only one runtime might be available together with some other tweaks on the available components/functionalities.
The UI should be able to morph based on the available capabilities.
Describe the solution you'd like
The available capabilities should be expressed via a single service and/or shared config.
The UI should enable/disable capabilities based on the provided information
What runtimes are installed
What runtime-specific capabilities are available (e.g. argo vs tekton)
What icons should be enabled on the launcher for the runtime specific pipelines
The icon should be provided from the runtime itself
Handle opening pipelines for unsupported runtime
Note: Any checks for specific runtimes (e.g. if runtime == 'kfp') should be removed
Note: Check if the schema service might suffice for providing all required information for ui-morphing
Note: Frontend sister PR / blocked by #2136
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Today, Elyra UI assumes all features are installed by default, including all different supported runtimes. When considering a real production deployment scenario, this might not be true, and only one runtime might be available together with some other tweaks on the available components/functionalities.
The UI should be able to morph based on the available capabilities.
Describe the solution you'd like
The available capabilities should be expressed via a single service and/or shared config.
The UI should enable/disable capabilities based on the provided information
runtime specific pipelines
Note: Any checks for specific runtimes (e.g. if runtime == 'kfp') should be removed
Note: Check if the schema service might suffice for providing all required information for ui-morphing
Note: Frontend sister PR / blocked by #2136
The text was updated successfully, but these errors were encountered: