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

Automatically update connection database to reflect available VMs #1833

Open
5 tasks done
jemrobinson opened this issue Apr 22, 2024 · 0 comments
Open
5 tasks done

Automatically update connection database to reflect available VMs #1833

jemrobinson opened this issue Apr 22, 2024 · 0 comments
Labels
enhancement New functionality that should be added to the Safe Haven release: non-essential Issues that at not essential to close for a release

Comments

@jemrobinson
Copy link
Member

✅ Checklist

  • I have searched open and closed issues for duplicates.
  • This is a request for a new feature in the Data Safe Haven or an upgrade to an existing feature.
  • The feature is still missing in the latest version.
  • I have read through the documentation.
  • This isn't an open-ended question (open a discussion if it is).

🍓 Suggested change

When we add/remove workspace VMs we have to update the Guacamole connection database (code is in provisioning > sre_provisioning_manager.py). We should make this automatic, instead of a separate step done at the end of dsh deploy sre.

🚂 How could this be done?

This could use e.g. Azure Functions or similar.

@jemrobinson jemrobinson added the enhancement New functionality that should be added to the Safe Haven label Apr 22, 2024
@jemrobinson jemrobinson added this to the Release 5.0.0rc2 milestone Apr 22, 2024
@JimMadge JimMadge added the release: non-essential Issues that at not essential to close for a release label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New functionality that should be added to the Safe Haven release: non-essential Issues that at not essential to close for a release
Projects
None yet
Development

No branches or pull requests

2 participants