At $WORK we have a Git repo set up by the devops team, where we can manage our junk by creating Terraform resources in our main AWS account. The state however

At $WORK we have a Git repo set up by the devops team, where we can manage our junk by creating Terraform resources in our main AWS account. The state however is always stored in a _separate AWS account_ that only the devops team can manage. I find this to be a reasonable way of working with TF. I agree that it is confusing though, because one is using $PROVIDER to both create things and manage those things at the same time, but conceptually from TF’s perspective they are very different things.