Found this terraform doc addressing my question terraform.io/language/settings/backends/local

Hey Christopher K.M Etou sorry I wasn't getting any notifications directly, glad you found the answer!

You might find some value in a recent video on this exact question here: YT: watch?v=Qg8VZsbaXxA&t=1416s. I can't post links yet, so you'll just have to add that query string to the YouTube URL ;)

Oh I know blast radius. It doesn't do anything to help. Consider having an infra or multiple generic projects that have elevated permissions and multiple projects with their own state. Each team has access only to their own state with the pipeline only able to fetch(but not change) remote state from the elevated projects Christopher K.M Etou

/dev/null I believe knowledge is a distributed system and the more we all contribute, the we all learn. Leon's article is the first block on how to modularize your terraform code.

The usecase you are describing is a valid one. Is there anything you found somewhere that could help complement Leon's article?

Hey /dev/null thanks for your inputs and yes I'm a newbie in Terraform, my focus was more on splitting your code into smaller pieces, each folder has its own state file so unless you're doing a terraform apply in all folders using something such as a CI/CD platform your code would definitely be much safer in a single repo, could you elaborate on environments, if you're pointing towards workspaces those are being deprecated and will only be available for terraform cloud backend/state, if you're referring to prod/dev env then this folder structure also works. While modules may help, that wasn't the focus of my article.

Thanks!