[Feature][config-ui] Dynamic UI

[klesh]

Search before asking

• [X] I had searched in the issues and found no similar feature requirement.

Description

1. #1411
2. config-ui to utilize this api, and provide a checkbox list on create pipeline page for user to select what they wanted to run.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[e2corporation]

@klesh "Dynamic UI" is a misleading title, this ticket should be better titled "Add Subtasks Selector to Blueprint Normal Mode UI".

[klesh]

@e2corporation This epic is not only about "Add Subtasks Selector to Blueprint Normal Mode UI". In long term, we want "Data Integration" and Places like that to be generated dynamically based on Server-Side information. It is important because someday people would have private plugins which we can't predefine in config-ui, and we would like users to be able to manage these private plugins via config-ui. In contrast, users may also delete/disable existing plugins, and the interface should act accordingly to avoid confusion. This is a long-term epic issue, my plan is to do it in multiple iterations. What do you think?

[e2corporation]

@klesh I understand the concept of having Dynamic Connections, I know what needs to be done to achieve this and I have my own plans optimizing the configuration. My problem is that this knowledge of "People have private plugins which need to be defined in UI" has not been mentioned by Louis our Product manager, nor has the feature been requested in a formal ticket with accurate details. Instead, the backend team is opening "refactor" tickets on their own to change core functionality on UI without me having any input. It's also making it difficult to focus on feature development when other developers are refactoring the system while I am trying to get features built for this milestone. This is not proper coordination. "users may also delete/disable existing plugins" has also never been mentioned in team meetings or logged issues as a normal use case of the application.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.