Deciding on the Correct Locations / Configurations for New Usages

[salvis2]

This repo has grown a lot since @yuvipanda and I set it up! There's a lot of work being done by STScI on their deployments and by myself on hackweek-specific deployments, as well as others, I'm sure. However, a lack of coordination on my part has left several of these examples in strange spots and there isn't really any documentation to help newcomers to the repo figure it out. So I wanted to try and get a sense of where everyone thinks new examples should go.

There are a couple categories of "new examples" that can be distinguished:

• Terraform configurations for new cloud providers - mainly GCP and Azure for now. We specifically named folders aws/ and aws-creds/, so I'm guessing that we would have a similar naming convention once there are some GCP and Azure configurations. Do we want to make a new layer of folders so that the top layer is just a cloud provider?
• Terraform configurations for specific use cases - my main thought here is the hackweek-template-infrastructure branch that I've set up. I did that with the thought of it being a feature branch, but since Terraform only looks in the current directory for configuration, we could easily have example configurations in an examples/ folder, maybe under each cloud provider once more are up. Thoughts?
• Terraform configurations for more flexible, general use - focusing for now on master vs unmanaged-nodegroups. We are slowly building this repo up to encompass more general deployment options. Do we want to make an effort to consolidate most of the work in the two previously-mentioned branches into one more-configurable deployment? Should we make this a module?

Would love to hear input from some STScI people on what would be helpful for y'all and where y'all can help out. I don't think anyone here is a Terraform expert so putting our heads together should be helpful!