3037a4f519
Fixed the Node Configuration for Apigee PAYG specific Environments. Removed current_aggregate_node_count as it is a read-only field and cannot be taken as an input for the Apigee Environment Terraform resource. Changes committed: modified: blueprints/cloud-operations/apigee/README.md modified: blueprints/cloud-operations/apigee/variables.tf modified: modules/apigee/README.md modified: modules/apigee/main.tf modified: modules/apigee/variables.tf modified: tests/blueprints/cloud_operations/apigee/fixture/variables.tf modified: tests/modules/apigee/fixture/variables.tf
Terraform end-to-end blueprints for Google Cloud
This section provides 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 - Active Directory Federation Services, Cloud Asset Inventory feeds for resource change tracking and remediation, Fine-grained Cloud DNS IAM via Service Directory, Cloud DNS & Shared VPC design, Delegated Role Grants, Networking Dashboard, Managing on-prem service account keys by uploading public keys, Compute Image builder with Hashicorp Packer, Packer example, Compute Engine quota monitoring, Scheduled Cloud Asset Inventory Export to Bigquery, Configuring workload identity federation for Terraform Cloud/Enterprise workflow, TCP healthcheck and restart for unmanaged GCE instances, Migrate for Compute Engine (v5) blueprints, Configuring workload identity federation to access Google Cloud resources from apps running on Azure
- data solutions - GCE and GCS CMEK via centralized Cloud KMS, Cloud Composer version 2 private instance, supporting Shared VPC and external CMEK key, Cloud SQL instance with multi-region read replicas, Data Platform, Spinning up a foundation data pipeline on Google Cloud using Cloud Storage, Dataflow and BigQuery, #SQL Server Always On Groups blueprint, Data Playground
- factories - The why and the how of Resource Factories, Google Cloud Identity Group Factory, Google Cloud BQ Factory, Google Cloud VPC Firewall Factory, Minimal Project Factory
- GKE - Binary Authorization Pipeline Blueprint, Storage API, Multi-cluster mesh on GKE (fleet API), GKE Multitenant Blueprint, Shared VPC with GKE support
- networking - Decentralized firewall management, Decentralized firewall validator, Network filtering with Squid, Network filtering with Squid with isolated VPCs using Private Service Connect, HTTP Load Balancer with Cloud Armor, Hub and Spoke via VPN, Hub and Spoke via VPC Peering, Internal Load Balancer as Next Hop, Nginx-based reverse proxy cluster, On-prem DNS and Google Private Access, Calling a private Cloud Function from On-premises, Hybrid connectivity to on-premise services through PSC, PSC Producer, PSC Consumer, Shared VPC with optional GKE cluster
- serverless - Creating multi-region deployments for API Gateway
- third party solutions - OpenShift on GCP user-provisioned infrastructure, Wordpress deployment on Cloud Run
For more information see the individual README files in each section.