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
i think using the parameter "use_explicit_dry_run_spec" with a similar logic than regular_service_perimeter could work.
See: https://github.com/terraform-google-modules/terraform-google-vpc-service-controls/blob/master/modules/regular_service_perimeter/main.tf#L214
The end goal would be to create a bridge perimeter in dry-run mode, and also have the ability to enforce it when a user wants to
Additional information
No response
The text was updated successfully, but these errors were encountered:
TL;DR
Currently the module bridge_service_perimeter doesn't support dry run mode.
When creating it, it creates it under "enforced" mode in GCP UI
Terraform Resources
google_access_context_manager_service_perimeter Link: https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/access_context_manager_service_perimeter
Detailed design
i think using the parameter "use_explicit_dry_run_spec" with a similar logic than regular_service_perimeter could work. See: https://github.com/terraform-google-modules/terraform-google-vpc-service-controls/blob/master/modules/regular_service_perimeter/main.tf#L214 The end goal would be to create a bridge perimeter in dry-run mode, and also have the ability to enforce it when a user wants to
Additional information
No response
The text was updated successfully, but these errors were encountered: