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

Make machine types and available IDEs accessible via the API #16865

Open
filiptronicek opened this issue Mar 15, 2023 · 2 comments
Open

Make machine types and available IDEs accessible via the API #16865

filiptronicek opened this issue Mar 15, 2023 · 2 comments
Labels
feature: public-api Issues relating to Public API meta: never-stale This issue can never become stale meta: stale This issue/PR is stale and will be closed soon

Comments

@filiptronicek
Copy link
Member

Is your feature request related to a problem? Please describe

Clients may want to have their own "start a workspace" experience. Practically speaking, for the https://github.com/gitpod-samples/Gitpod-Raycast-Extension, IDEs and machine types have to be hard-coded into the code to be able to start workspaces properly.

This though itself is problematic (not just because of the problems arising with maintaining) - for other installation hosts like in a Gitpod Dedicated scenario, these machine types just cannot be gotten.

Describe the behaviour you'd like

Two read-only API endpoints:

  1. for listing all IDEs along with their versions (similar to what we implement in ide-service, but in the Public API) - getIDEOptions
  2. for listing all machine types available on the install for the currently logged-in user - getSupportedWorkspaceClasses
@loujaybee
Copy link
Member

loujaybee commented Mar 17, 2023

Thanks for raising, @filiptronicek this would be useful. Not sure I'd have as separate endpoints (depends on payload size), as general meta information seems useful, but we could discuss when picking up 🙏

@stale
Copy link

stale bot commented Jun 17, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jun 17, 2023
@filiptronicek filiptronicek added the meta: never-stale This issue can never become stale label Jun 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: public-api Issues relating to Public API meta: never-stale This issue can never become stale meta: stale This issue/PR is stale and will be closed soon
Projects
None yet
Development

No branches or pull requests

2 participants