a12da693a3
* added support 2nd generation cloud function * changed function_version to a simple boolean v2 removed memory_2ndGen * will use the var.v2 to add the invoker role * removed the list uisng compact and formated the code * formated the code and added conditional feature * formated the code * added formating * resolved the merge conflict * Update readme * Create local function object * added secret_volumes and secret_environment_variables for CF V2 Co-authored-by: Julio Castillo <jccb@google.com> |
||
|---|---|---|
| .. | ||
| cloud-operations | ||
| data-solutions | ||
| factories | ||
| gke | ||
| networking | ||
| serverless | ||
| third-party-solutions | ||
| README.md | ||
README.md
Terraform end-to-end blueprints for Google Cloud
This section networking blueprints that implement core patterns or features, data solutions blueprints that demonstrate how to integrate data services in complete scenarios, cloud operations blueprints that leverage specific products to meet specific operational needs, GKE and Serverless blueprints, and factories that implement resource factories for the repetitive creation of specific resources.
Currently available blueprints:
- cloud operations - Resource tracking and remediation via Cloud Asset feeds, Granular Cloud DNS IAM via Service Directory, Granular Cloud DNS IAM for Shared VPC, Compute Engine quota monitoring, Scheduled Cloud Asset Inventory Export to Bigquery, Packer image builder, On-prem SA key management, TCP healthcheck for unmanaged GCE instances, HTTP Load Balancer with Cloud Armor
- data solutions - GCE/GCS CMEK via centralized Cloud KMS, Cloud Storage to Bigquery with Cloud Dataflow with least privileges, Data Platform Foundations, SQL Server AlwaysOn availability groups blueprint, Cloud SQL instance with multi-region read replicas, Cloud Composer version 2 private instance, supporting Shared VPC and external CMEK key
- factories - The why and the how of resource factories
- GKE - GKE multitenant fleet, Shared VPC with GKE support, Binary Authorization Pipeline, Multi-cluster mesh on GKE (fleet API)
- networking - hub and spoke via peering, hub and spoke via VPN, DNS and Google Private Access for on-premises, Shared VPC with GKE support, ILB as next hop, PSC for on-premises Cloud Function invocation, decentralized firewall
- serverless - Multi-region deployments for API Gateway
- third party solutions - OpenShift cluster on Shared VPC
For more information see the individual README files in each section.