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

Consider separating Terraform/Cloud-Sandbox deployment into separate repo #65

Open
mwengren opened this issue Jul 21, 2023 · 2 comments
Assignees

Comments

@mwengren
Copy link
Member

Related to better defining the workflow for Cloud Sandbox end users to access the platform, we discussed in meetings the idea of separating out the Terraform and deployment or infrastructure-related code into a separate repo.

This would allow new users to have a simplified version of the user-facing code deployed automatically to their home directories when they log into the Sandbox environment.

TBD: what portions of this repo belong in a new Terraform/infrastructure repo and what belongs in user home environments.

@KatherinePowell-NOAA KatherinePowell-NOAA added this to the Establish / support Sandbox access for NOAA personnel & non-NOAA collaborators milestone Aug 31, 2023
@KatherinePowell-NOAA KatherinePowell-NOAA removed this from the Establish / support Sandbox access for NOAA personnel & non-NOAA collaborators milestone Aug 29, 2024
@Michael-Lalime
Copy link
Contributor

@mwengren can this issue be closed or is it still relevant? We are looking over these issues and trying to clean them up.

@mwengren
Copy link
Member Author

I don't have a strong opinion about this. I think this was entered during a meeting (quite a while ago). I'd say if we don't have any plans to do this, go ahead and close it out.

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

3 participants