Region in name pattern

I’ve noticed in the documentation that in some cases you include the REGION in the name of resources, for instance for workspaces.

terraform {
  backend "remote" {
    organization = "ORG" # replace with your terraform cloud account org
    workspaces {
      name = "<%= expansion(':MOD_NAME-:ENV-:REGION-:INSTANCE') %>"

Is there a particular reason for including region in name of the resources? Or is it more to ensure the names are unique?

Thank you!

Region is included just in case you have to go multi-region in the future. Don’t think most actually will go multi-region, but when they do have to, it can be painful :weary: And included as the default based on that pain level. :rofl:

Though this person was to be able to migrate from single region to multi-region pretty smoothly :grinning_face_with_smiling_eyes: