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

UI to edit the resource config UI ordering and config field inter-dependencies #32

Open
nmbr7 opened this issue Sep 1, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@nmbr7
Copy link
Member

nmbr7 commented Sep 1, 2024

  • Currently the resource config UI shows all the config fields.
  • For a better user experience, it should show only the base config fields that are not dependent on other config fields.
  • Based on the selection/input field of the base config fields, we should show the dependent config fields, resulting in a better user experience.
  • We need to create a UI to edit the resource config UI so that the users can update the resource config ordering and inter-resource config dependencies.
  • The UI changes done by the user should be serialized into a JSON representing a DAG of resource config fields.
  • Once the changes are requested, it should trigger a git pull request to the backend repo.
    • We could also update and create a new JSON file for the upstream cloud resource JSON file with the data we collect.
    • Since the structure of the config UI will change, we will need to add/update the dynamic UI rendering template in the front end which respects the inter-resource dependencies. However, this could be covered by the changes required for the UI editor changes in the first place.

This new UI editor will act as the base for crowd-sourcing the UI changes since we have thousands of resources and related configs, and manually changing and verifying these will be expensive work.

@nmbr7 nmbr7 converted this from a draft issue Sep 1, 2024
@nmbr7 nmbr7 added the enhancement New feature or request label Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant