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

Provider configuration UX #372

Open
idagelic opened this issue Apr 9, 2024 · 0 comments
Open

Provider configuration UX #372

idagelic opened this issue Apr 9, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@idagelic
Copy link
Member

idagelic commented Apr 9, 2024

Is your feature request related to a problem? Please describe.
There are plans to add many more Providers other than the Docker Provider to Daytona. The properties they need for configuration of e.g. VM characteristics such as the OS/arch combination need to be strictly defined in a specific format like image name, build name+version etc.

These values are hard to guess for the user and "recognition over recall" would be necessary to ensure good UX. This is an easier task for web apps than terminals because of the interactivity regarding dynamic substring-based suggestions when typing in the input values and simple and efficient dropdown components.

We need to research a way to implement this kind of UX enhancement that would combine the suggestions from a fixed set of suggestion strings (from a e.g. provider-specific config file) as well as allowing custom input for more specific entries.

This kind of component should be made as a custom Charm piece that is similarly designed to the existing TUI and should work well with any input type combination from a predefined provider config format.

@idagelic idagelic added the enhancement New feature or request label Apr 9, 2024
@idagelic idagelic self-assigned this Apr 9, 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
None yet
Development

No branches or pull requests

1 participant