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

Prevent to create an environnement with existing name #32

Open
pierrepo opened this issue Jul 6, 2020 · 4 comments
Open

Prevent to create an environnement with existing name #32

pierrepo opened this issue Jul 6, 2020 · 4 comments
Assignees

Comments

@pierrepo
Copy link
Contributor

pierrepo commented Jul 6, 2020

User can provide any name for its environment.

If 2 environments have the same name, conflicts could occur.

On should prevent the creation of an environment with an already existing name.

@jtpio
Copy link
Member

jtpio commented Jul 7, 2020

It might still be useful to be able to reuse an existing name.

For example a teacher could prepare a new environment with the same name, keeping the old one available while the new one is building. Once the new one is available, the old one can be removed by clicking on the remove button (a bit like a rolling upgrade).

@jtpio
Copy link
Member

jtpio commented Jul 7, 2020

An alternative could be to display a hint in the dialog window, by checking the list of existing environments client side (without enforcing it server side)

@pierrepo
Copy link
Contributor Author

pierrepo commented Jul 7, 2020

Having twice (or more) the same env name could be very confusing.

Even the case of a rolling update might not be easily handled by teachers.

display a hint in the dialog window, by checking the list of existing environments client side

Yes. Definitely.

@pierrepo
Copy link
Contributor Author

pierrepo commented Jul 8, 2020

Actually, this reminds me the red or green tick that appears nearby the name of a gihub repo when you create one:
Peek 08-07-2020 09-26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants