This message was deleted.
# general
s
This message was deleted.
s
You could create a single stack with multiple providers in it.
You could prolly leverage organizations too.
i
yeah i have it looping over accounts and creating a provider for each one atm which i think will work, it of course then each resource needs a name that’s unique to the stack
l
For repeated configuration in multiple accounts (e.g. adding IAM roles so that my admin users in my identity account can assume-rule into each account), I use a single project with multiple stacks, and the stack config specifies the provider. For a single configuration that applies across multiple accounts (e.g. VPC peering) I use a (different) single project with a single stack, and the providers are set up in code.
i
Thanks @little-cartoon-10569 that’s super useful and makes a lot of sense
We’re only on the team starter plan atm, so suspect we’ll run the risk of running out of available stacks if I adopt that model, but it does sound the cleanest
l
20 stacks per project, unlimited projcets.. you should be ok.
Especially if you wrap your repeated code in a class. Then your project might only be 1 or 2 lines long, and it's minimal overhead having 2 projects in order to have 40 stacks..
i
oh i read it as 20 stacks total, across all projects
that changes things significantly if that’s not the case!
appears not to be the case, searching here - they do mean 20 stacks total.. if you have 2 projects with 10 stacks in each one, you’d be at the limit for the “team starter” plan
a
This has been discussed as per that thread. It (the limit) is 20 total stacks across all projects @little-cartoon-10569.
👍 2