update

examples/vpc-transit-gateway-attachment/provider.vpc-transit-gateway.tf

@@ -0,0 +1,20 @@
+# establish the additional providers needed for self and peer. For commercial, there will be several peers
+# though we have not worked out that configuration. We may split the provider parts out to a different file.
+
+provider "aws" {
+  alias   = "network_account"
+  region  = var.region
+  profile = var.network_account_profile
+}
+
+provider "aws" {
+  alias   = "tgw_self"
+  region  = var.region
+  profile = var.network_account_profile
+}
+
+provider "aws" {
+  alias   = "tgw_peer"
+  region  = var.region == "us-gov-east-1" ? "us-gov-west-1" : "us-gov-east-1"
+  profile = var.network_account_profile
+}

examples/vpc-transit-gateway-attachment/vpc-transit-gateway.tf

@@ -1,24 +1,3 @@
-# establish the additional providers needed for self and peer. For commercial, there will be several peers
-# though we have not worked out that configuration. We may split the provider parts out to a different file.
-
-provider "aws" {
-  alias   = "network_account"
-  region  = var.region
-  profile = var.network_account_profile
-}
-
-provider "aws" {
-  alias   = "tgw_self"
-  region  = var.region
-  profile = var.network_account_profile
-}
-
-provider "aws" {
-  alias   = "tgw_peer"
-  region  = var.region == "us-gov-east-1" ? "us-gov-west-1" : "us-gov-east-1"
-  profile = var.network_account_profile
-}
-
 # this is a three part setup, but due to proper referencing it will do them in the correct order
 # first, we need to get data, then do self, and then do peer
 # this expects in the network account for the environment, two managed prefixe lists are setup, one for all CIDR blocks handled