Hello everyone. So I have a question about project organization: I created a repo to build my infrastructure code (with sst), but I'm using multiple regions (namely I have some legacy code and RDS running in us-west-2 and the new things are running in us-east-1) and not sure what is the best approach to manage that. The first thing that came to my mind was to split the repo creating root folders per region and each folder having its own

sst.json

Does it make sense or there's a more elegant way? btw, should I ask this type of question here or in the #sst channel? 🙂

Are you planning to add to your legacy stacks? And do you need to reference the resources you have there? If you don’t, then separating them like you said makes sense.

In the first phase, I'm planning to create a serverless API on top of legacy resources like the RDS. In phase two the idea is to redesign the services to become independent of the legacy stack,

If that's the future plan then maybe go with splitting them up.