* Remove bridge perimeters
* Update FAST stages
* Allow project ids in perimeter definitions
* Preserve order order for ingress/egress policies
* Use CAI
* Use CAI
* Fix tests
* Add perimeter factory
Proposal to allow the management of perimeters in yaml factory.
Project discovery is extended to multiple perimeters with query filtering.
Doc clean uo
* default perimeters desc to null
* linting
* Revert changes to FAST
* Remove test and schema from FAST
* Align vars and perimeter factory
* Interpolate resource_sets in more places
* Silence linter
* Update README.md
---------
Co-authored-by: Julio Castillo <jccb@google.com>
Co-authored-by: Ludovico Magnocavallo <ludo@qix.it>
* Allow empty string for 'identity_type' supported by Google provider and use correct value name for ingress 'identity_type'
* Sanitizing variables as the logical operators in Terraform do not short-circuit.
* vpc-sc : allow null for identity_type
* cloudsql-instance : fmt
* vpc-sc: tfdoc
* modules/vpc-sc: update the test result for the identity_type field
* cloudsql-instance: remove empty line
* first implementation
* minimal output
* split service perimeters in regular and bridge
* tests and fixes
* new vpc-sc implementation
* remove providers file used for testing
* remove provider used during development
- Ensure all variables and outputs are sorted
- Ensure all variables and outputs have a description
- Add data-solutions/data-platform-foundations to linter
Fix all modules to follow these new conventions.
* Add VPC-SC support for Regions, device policy and access policy dependency.
* fix compute mig module test
* Fixes
* Fix example
Co-authored-by: Ludovico Magnocavallo <ludomagno@google.com>
