> I just wanted to clarify: are you referring to this pattern?
Does TF support count on modules now?! The pattern I was referring to is akin to having an `enabled` var that you define in _every_ module (there are ways to make this easier to do [0]) and inside of each module you have a
count - Creates multiple instances of a module from a single module block.
for_each - Creates multiple instances of a module from a single module block.
providers - Passes provider configurations to a child module. If not specified, the child module inherits all of the default (un-aliased) provider configurations from the calling module.
depends_on - Creates explicit dependencies between the entire module and the listed targets.
I hope this doesn't come across as snarky, I just wanted to share the doc link :)
Does TF support count on modules now?! The pattern I was referring to is akin to having an `enabled` var that you define in _every_ module (there are ways to make this easier to do [0]) and inside of each module you have a
Then you use the typical `count: foo == bar ? 1:0` trick where some part of the `foo/bar` conditional ropes in local.make_the_rds_instance[0]: https://github.com/cloudposse/terraform-null-label/tree/main