Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable UI capabilities based on optionally installed features #2135

Open
5 tasks
lresende opened this issue Sep 13, 2021 · 3 comments
Open
5 tasks

Enable UI capabilities based on optionally installed features #2135

lresende opened this issue Sep 13, 2021 · 3 comments

Comments

@lresende
Copy link
Member

lresende commented Sep 13, 2021

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

@ajbozarth
Copy link
Member

FYI This is primarily to support #2136

@akchinSTC akchinSTC modified the milestones: 3.3.0, 3.4.0 Oct 26, 2021
@akchinSTC akchinSTC modified the milestones: 3.4.0, 3.5.0 Dec 3, 2021
@marthacryan marthacryan removed their assignment Jan 11, 2022
@akchinSTC akchinSTC modified the milestones: 3.5.0, Backlog Medium Term Jan 13, 2022
@juliusvonkohout
Copy link

Do you have an ETA for this feature?

@kevin-bates
Copy link
Member

#3114 may be all that is necessary for this since the exposed tiles are sensitive to the desired runtimes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants