Files
hunfabric/modules
Ludovico Magnocavallo f62b9362a2 ILB for appliances example (#122)
* rename infrastructure folder to networking

* example WIP: VPCs

* move ip forwarding to its own variable in compute-vm module

* add per-instance metadata support to compute-vm module

* ipip tunnels on linux savepoint

* simple multinic gateways example

* remove stale files

* resolve conflicts

* update diagram

* rename folder

* use a template for gw cloud config, rename some resources and files

* Update README.md

* Update README.md

* add basic plan tests for all networking e2e examples

* fix test for foundations/environments e2e example

* fix shared vpc e2 example count error in gke node service account permissions

* use module path for assets in onprem e2e example

* use project id from module in ilb e2e example

* add mising boilerplates in tests

* run examples tests in ci

* update module's README

* rename ilb example

* Update README.md

* fix rp_filter configuration

* README

* Update README.md

* Update README.md

* Update README.md

* update CHANGELOG

* update CHANGELOG

* Update README.md
2020-08-15 10:12:43 +02:00
..
2020-06-09 16:03:10 +02:00
2020-08-08 11:04:53 +02:00
2020-06-24 18:13:45 +02:00
2020-06-09 17:21:07 +02:00
2020-06-03 08:43:10 +02:00
2020-06-12 12:07:28 +02:00
2020-07-08 21:39:50 +02:00
2020-05-13 07:54:46 +02:00
2020-08-15 10:12:43 +02:00
2020-07-10 07:22:57 +02:00

Terraform modules suite for Google Cloud

The modules collected in this folder are designed as a suite: they are meant to be composed together, and are designed to be forked and modified where use of third party code and sources is not allowed.

Modules try to stay close to the low level provider resources they encapsulate, and they all share a similar interface that combines management of one resource or set or resources, and the corresponding IAM bindings.

Authoritative IAM bindings are primarily used (e.g. google_storage_bucket_iam_binding for GCS buckets) so that each module is authoritative for specific roles on the resources it manages, and can neutralize or reconcile IAM changes made elsewhere.

Specific modules also offer support for non-authoritative bindings (e.g. google_storage_bucket_iam_member for service accounts), to allow granular permission management on resources that they don't manage directly.

Foundational modules

Networking modules

Compute/Container

Data

Development

Security

Serverless