You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I was curious if you had ideas on patterns for how this module might be used or extended to support partitions other than aws? In particular, aws-us-gov, but there is also aws-cn, aws-iso, and aws-iso-b.
Right now, the module has providers aliased with names specific to each region... I suppose we could effectively ignore that? For example, in our root module map a us-gov-west-1 provider to the aliased us-west-1 provider, us-gov-east-1 to us-east-1, and use var.target_regions to scope things to just those two regions...
Or would it make more sense to just add aliased providers for each region in other partitions to this module? Or to somehow create another module or layer of abstraction for each partition?
The text was updated successfully, but these errors were encountered:
@lorengordon
Mapping different regions to aliases should just work because this module setup same resources for aliased providers. I'm afraid additiing aliased providers for those partitions, however, would be troublesome because users would be required to provide these aliases even if they don't activate them in their accounts.
Originally I had no plan to support those partitions simply because I haven't had any chance working with them. I'm happy to discuss if you have any idea or propsal though!
@nozaq With the limitations on using expressions when specifying values for the provider/providers attributes of resources/modules, it is hard to see how to make it work with a single top-level module... I could maybe see how we could have partition-specific modules, each defining all the aliased providers for the regions in each partition. Perhaps the top-level module then becomes a single-region, single-provider wrapper around all the "baseline" modules? Something like:
Hello, I was curious if you had ideas on patterns for how this module might be used or extended to support partitions other than
aws
? In particular,aws-us-gov
, but there is alsoaws-cn
,aws-iso
, andaws-iso-b
.Right now, the module has providers aliased with names specific to each region... I suppose we could effectively ignore that? For example, in our root module map a
us-gov-west-1
provider to the aliasedus-west-1
provider,us-gov-east-1
tous-east-1
, and usevar.target_regions
to scope things to just those two regions...Or would it make more sense to just add aliased providers for each region in other partitions to this module? Or to somehow create another module or layer of abstraction for each partition?
The text was updated successfully, but these errors were encountered: