Add end-to-end tests (apply, plan, destroy) for examples.
When run, `tests/examples_e2e`:
1. Create an environment for tests to run (folder, project vpc network)
2. For each marked example (with `e2e` tftest directive), run apply, plan, destroy
3. Verify:
* no failure in apply
* empty plan after apply
* no failure during destroy
4. When all tests are done, destroy test environment
More details in `tests/examples_e2e/README.md`
* Added ProtectedApplication feature to GKE Backup
* Fixed location name and added example
* Modified test module
* Changed test
* Changed test
* Changed test
* Restore old "all_namespaces" logic
* Bug fix
* Ran fmt on README example
* Modified variable structure
* Fix test
* Fix
## net-lb-int
* Fix error on apply of example:
```
Error creating RegionBackendService: googleapi: Error 400: Invalid value for field 'resource.backends[0].balancingMode': 'UTILIZATION'. Balancing mode must be CONNECTION for an INTERNAL backend service., invalid
```
* remove unused `balancing_mode` variable, as only one value is possible anyhow
## net-lb-ext
* update in the `backends` description
## net-lb-proxy-int
* update in the `backends` description
## net-lb-app-int
* added validation of `balancing_mode`
* fixed other validations
## net-lb-app-ext
* added validation of `balancing_mode`
* fixed other validations
* removed validation for `locality_lb_policy` as this variable is not used in this module
Closes: #1767
For objects that are not simple attributes of the resource (i.e.
objects, lists) allow specifing subset of values that needs to be
verified.
In case of lists, count of list objects must match, but if values are
objects / dicts, they can be specified as empty dicts which should pass
all the checks, as no keys are specified.
* Define and adopt standard IP ranges for FAST networking
This PR documents and adopts a consistent IP address plan for FAST
networking stages
Fixes#1644
* Fix documented aggregated ranges for FAST
* Fix tests
* Fix ip ranges in documentation
* Fix NVA stages README
* `gke-cluster-standard`: add optional kube state metrics
* `gke-cluster-autopilot`: add optional kube state metrics
* FAST: add kube state metrics support for GKE
* blueprints/gke: add kube state metrics support
* Bump up the provider version to `v4.82.0`
* gke-cluster-standard: upgrade `monitoring_config` to use object style. Add tests.
* gke-cluster-standard: update docs
* gke-cluster-autopilot: move gateway_api_config block (cosmetic change)
* gke-cluster-autopilot: update docs and fix typos
* Update blueprints due to `monitoring_config` changes in `gke-cluster-standard`.
* Update FAST due to `monitoring_config` changes in `gke-cluster-standard`.
* Update docs for affected blueprints and FAST stages
* gke-cluster-autopilot: add support for network tags
* gke-cluster-autopilot: add validation for network tags
* gke-cluster-autopilot: expand README and fix some typos
* gke-cluster-autopilot: fix Cloud DNS section in README
Removed a reference to Standard clusters and updated the section to include a warning because the new versions of Autopilot clusters can only use Cloud DNS and it is pre-configured by default so the example in the README does not apply to them.
* gke-cluster-autopilot: cosmetic fixes in README
* gke-cluster-autopilot: rollback validation on network tags var
* gke-cluster-autopilot: rollback docs string update for network tags var
* gke-cluster-autopilot: rollback some updates to README
* gke-cluster-autopilot: remove dead code
* gke-cluster-autopilot: add a tftest for network tags
* gke-cluster-autopilot: fix a tftest
Luca Prete
Simone Ruffilli
Wiktor Niesiobędzki
luigi-bitonti
Ludovico Magnocavallo
jeroenmonteban
Julio Castillo
apichick
Anmol Sachdeva
Jason Steenblik
Oliver Frolovs
Dave Gulli
Pierre Formont
simonebruzzechesse