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

[P&S Initiative] VEDA Objective JH-2: Add ability to remember previously used custom images and repositories to the logged in environment selector #5410

Open
jnywong opened this issue Jan 24, 2025 · 0 comments
Labels
external Requires external collaboration

Comments

@jnywong
Copy link
Member

jnywong commented Jan 24, 2025

Motivation

When a user logs into the hub, they are presented with (among other things) a way to select the environment they want to use. One of the options is to specify their own Dcker image (‘bring your own image’), and another is to specify a GitHub repository from which an image will be dynamically built (‘bring your own repo’). It would be very helpful if both these remember prior options the user has used so they can immediately go back to a prior environment they have used instead of having to type it in each time.

Description

As part of this objective, we’ll also be doing a conversion of the code-base from typed JavaScript to TypeScript. We expect this to take little time now because the code base is small, and enable us to move faster both for this objective and in the future.

Success Criteria

  • Bring your own image features remember previously used options so users can quickly select them
  • The code-base is converted into TypeScript
  • Dynamic image building has been rolled out to all hubs

Personnel

@jnywong jnywong changed the title [P&S Initiative]: VEDA Objective JH-2: Add ability to remember previously used custom images and repositories to the logged in environment selector [P&S Initiative] VEDA Objective JH-2: Add ability to remember previously used custom images and repositories to the logged in environment selector Jan 24, 2025
@jnywong jnywong added the external Requires external collaboration label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external Requires external collaboration
Projects
None yet
Development

No branches or pull requests

1 participant