Extend integration tests to run in two regions

[bobbyiliev]

Fixes #560

[SangJunBak]

Code looks good to me! Unfortunate that users with multiple regions will have to duplicate a lot of their objects, but doesn't seem like there's a terraform-only solution for this.

[benesch]

Unfortunate that users with multiple regions will have to duplicate a lot of their objects, but doesn't seem like there's a terraform-only solution for this.

If they're looking to create the same objects in multiple regions, they can use Terraform's take on loops (count) to automatically create the same objects in multiple regions—is that the kind of thing you meant?

[bobbyiliev]

Indeed, this can be done with a loop:

variable "regions" {
  type    = list(string)
  default = ["aws/us-west-2", "aws/us-east-1"]
}

resource "materialize_cluster" "multi_region_clusters" {
  count   = length(var.regions)
  name    = "cluster"
  comment = "Cluster in ${var.regions[count.index]}"
  region  = var.regions[count.index]
}

My idea behind the test here is to make sure that users can rely on the default region in their provider configuration, but also be able to spin up ad-hoc resources in different regions by overriding the default one in the resources themselves.

I think that in most cases, people only manage resources in 1 region, and if they wanted to replicate their whole setup in another region they would just change the default region provider configuration value.

[SangJunBak]

If they're looking to create the same objects in multiple regions, they can use Terraform's take on loops (count) to automatically create the same objects in multiple regions—is that the kind of thing you meant?

Something like that, but I could still see it getting messy with the count/for_each syntax. I think Bobby's solution:

I think that in most cases, people only manage resources in 1 region, and if they wanted to replicate their whole setup in another region they would just change the default region provider configuration value.

Was what I was thinking of!