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
| <aname="input_billing_account_id"></a> [billing\_account\_id](#input\_billing\_account\_id)| The GCP billing account in your organization. |`string`| n/a | yes |
27
-
| <aname="input_billing_dataset_project_id"></a> [billing\_dataset\_project\_id](#input\_billing\_dataset\_project\_id)| GCP Project ID where the biquery table resides that holds billing data export. |`string`| n/a | yes |
28
-
| <aname="input_billing_org_id"></a> [billing\_org\_id](#input\_billing\_org\_id)| GCP organization ID that holds billing account |`string`| n/a | yes |
29
-
| <aname="input_kraken_sa_name"></a> [kraken\_sa\_name](#input\_kraken\_sa\_name)| Name of the service account to create for Kraken |`string`|`"mesh-kraken-service-tf"`| no |
27
+
| <aname="input_billing_org_id"></a> [billing\_org\_id](#input\_billing\_org\_id)| GCP organization ID that holds billing account. |`string`| n/a | yes |
| <aname="input_cloud_billing_export_project_id"></a> [cloud\_billing\_export\_project\_id](#input\_cloud\_billing\_export\_project\_id)| GCP Project where the BiqQery table resides that holds the Cloud Billing export to BigQuery. See https://cloud.google.com/billing/docs/how-to/export-data-bigquery|`string`| n/a | yes |
| <aname="input_kraken_sa_name"></a> [kraken\_sa\_name](#input\_kraken\_sa\_name)| Name of the service account to create for Kraken. |`string`|`"mesh-kraken-service-tf"`| no |
30
32
| <aname="input_landing_zone_folder_ids"></a> [landing\_zone\_folder\_ids](#input\_landing\_zone\_folder\_ids)| GCP Folders that make up the Landing Zone. The service account will only receive permissions on these folders. |`list(string)`| n/a | yes |
31
33
| <aname="input_org_id"></a> [org\_id](#input\_org\_id)| GCP Organization ID that holds the projects that generate billing data that the service account should import. |`string`| n/a | yes |
32
-
| <aname="input_project_id"></a> [project\_id](#input\_project\_id)| GCP Project ID where to create the resources. This is typically a 'meshstack-root' project |`string`| n/a | yes |
33
-
| <aname="input_replicator_sa_name"></a> [replicator\_sa\_name](#input\_replicator\_sa\_name)| Name of the service account to create for Replicator |`string`|`"mesh-replicator-service-tf"`| no |
34
+
| <aname="input_project_id"></a> [project\_id](#input\_project\_id)| GCP Project ID where to create the resources. This is typically a 'meshstack-root' project.|`string`| n/a | yes |
35
+
| <aname="input_replicator_sa_name"></a> [replicator\_sa\_name](#input\_replicator\_sa\_name)| Name of the service account to create for Replicator.|`string`|`"mesh-replicator-service-tf"`| no |
34
36
35
37
## Outputs
36
38
37
39
| Name | Description |
38
40
|------|-------------|
41
+
| <aname="output_cloud_billing_export_table_name"></a> [cloud\_billing\_export\_table\_name](#output\_cloud\_billing\_export\_table\_name)| The BigQuery table name containing the GCP Cloud Billing BigQuery export. |
39
42
| <aname="output_kraken_sa_email"></a> [kraken\_sa\_email](#output\_kraken\_sa\_email)| Kraken service account email. |
40
43
| <aname="output_kraken_sa_key"></a> [kraken\_sa\_key](#output\_kraken\_sa\_key)| Kraken service account key. |
41
44
| <aname="output_replicator_manual_setup"></a> [replicator\_manual\_setup](#output\_replicator\_manual\_setup)| Replicator service account setup information. |
| <aname="input_billing_dataset_project_id"></a> [billing\_dataset\_project\_id](#input\_billing\_dataset\_project\_id)| GCP Project ID where the biquery table resides that holds billing data export. |`string`| n/a | yes |
33
+
| <aname="input_cloud_billing_export_project_id"></a> [cloud\_billing\_export\_project\_id](#input\_cloud\_billing\_export\_project\_id)| GCP Project where the BiqQery table resides that holds the Cloud Billing export to BigQuery. |`string`| n/a | yes |
34
34
| <aname="input_landing_zone_folder_ids"></a> [landing\_zone\_folder\_ids](#input\_landing\_zone\_folder\_ids)| GCP Folders that make up the Landing Zone. The service account will only receive permissions on these folders. |`set(string)`| n/a | yes |
35
35
| <aname="input_meshstack_root_project_id"></a> [meshstack\_root\_project\_id](#input\_meshstack\_root\_project\_id)| GCP Project ID where to create the service account. This is typically a 'meshstack-root' project. |`string`| n/a | yes |
36
36
| <aname="input_org_id"></a> [org\_id](#input\_org\_id)| GCP Organization ID that holds the projects that generate billing data that the service account should import. |`string`| n/a | yes |
37
-
| <aname="input_sa_name"></a> [sa\_name](#input\_sa\_name)|name of the service account to create |`string`| n/a | yes |
37
+
| <aname="input_sa_name"></a> [sa\_name](#input\_sa\_name)|Name of the service account to create.|`string`| n/a | yes |
Attention. The created service account ${google_service_account.replicator_service.email} with the unique id '${google_service_account.replicator_service.unique_id}' needs a manual role assignment for the G Suite role 'Group Administrator' so necessary group operations can be performed domain-wide.
0 commit comments