Trying to add the vpc_service_control_attach_dry_run argument to an otherwise working implementation of the project factory module fails, it appears that that it's not exposed to the module.
You can also see that this variable is not listed as an input at the provider page, even though this variable appears supported in this repo.
When I add the variable vpc_service_control_attach_dry_run = true to the module arguments and then run terraform plan, I get an error like
on ../../modules/single_project/main.tf line 66, in module "project":
│ 66: vpc_service_control_attach_dry_run = "true"
│
│ An argument named "vpc_service_control_attach_dry_run" is not expected here.
This is the same error I get when adding nonsense variables to test, whereas I'm able to add other arbitrary variables defined in this repo to my code without the error.
Terraform v1.6.5
on linux_amd64
+ provider registry.terraform.io/hashicorp/google v5.27.0
+ provider registry.terraform.io/hashicorp/google-beta v5.27.0
+ provider registry.terraform.io/hashicorp/null v3.2.2
+ provider registry.terraform.io/hashicorp/random v3.6.1
+ provider registry.terraform.io/hashicorp/time v0.11.1
Your version of Terraform is out of date! The latest version
is 1.8.2. You can update by downloading from https://www.terraform.io/downloads.html
Additional information
Comparing it's usage to other valid arguments from this repo, it appears that this variable has not been correctly exposed in the metadata.yaml file
TL;DR
Trying to add the
vpc_service_control_attach_dry_run
argument to an otherwise working implementation of the project factory module fails, it appears that that it's not exposed to the module.You can also see that this variable is not listed as an input at the provider page, even though this variable appears supported in this repo.
Expected behavior
https://github.com/terraform-google-modules/terraform-google-project-factory/blob/58c4c7dbf00c5f39987b49706b215cf0c3b32e8f/variables.tf#L292
Setting
vpc_service_control_attach_dry_run
in the module should allow me to add a project to the dry-run configuration of a perimeter only. (Equivalent of settinguse_explicit_dry_run_specs
if I were working directly with the google_access_context_manager_service_perimeter resources.Observed behavior
When I add the variable
vpc_service_control_attach_dry_run = true
to the module arguments and then runterraform plan
, I get an error likeThis is the same error I get when adding nonsense variables to test, whereas I'm able to add other arbitrary variables defined in this repo to my code without the error.
Terraform Configuration
Terraform Version
Additional information
Comparing it's usage to other valid arguments from this repo, it appears that this variable has not been correctly exposed in the metadata.yaml file