eaa420534b
* feat(agent-engine): add support for container and custom image specs - Add container_config to deployment_files. - Add image_spec with build_args to source_config. - Make agent_framework optional and document supported values. - Implement dynamic specs for container and source deployments. - Add examples and automated tests for new deployment types. * chore: update Google provider version to 7.28.0 across modules Mechanical update of versions.tf and versions.tofu files using tools/versions.py. * feat(agent-engine): refactor for container deployments and API alignment - Group deployment settings under 'deployment_config' (renamed from 'deployment_files'). - Support container-based deployments via 'container_config' and 'image_spec'. - Refactor 'source_files_config' (renamed from 'source_config') to include mutually exclusive 'python_spec' and 'image_spec'. - Support 'developer_connect_config' as a source code type. - Group engine settings (framework, env, secrets) under 'agent_engine_config'. - Add support for 'memory_bank_config' persistent memory. - Overhaul reasoning engine resources with dynamic blocks to match provider schema. - Update all documentation examples, add TOC, and refresh test inventories. * Update dynamic python_spec block and related example yamls * Ignore changes setting for developer_connect_source under lifecycle management * fixing review comments for `try` and default path for `source_path` --------- Co-authored-by: Hemanand <hemr@google.com> Co-authored-by: Julio Castillo <jccb@google.com>
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.
These modules are not necessarily backward compatible. Changes breaking compatibility in modules are marked by major releases (but not all major releases contain breaking changes). Please be mindful when upgrading Fabric modules in existing Terraform setups, and always try to use versioned references in module sources so you can easily revert back to a previous version. Since the introduction of the moved block in Terraform we try to use it whenever possible to make updates non-breaking, but that does not cover all changes we might need to make.
These modules are used in the examples included in this repository. If you are using any of those examples in your own Terraform configuration, make sure that you are using the same version for all the modules, and switch module sources to GitHub format using references. The recommended approach to working with Fabric modules is the following:
-
Fork the repository and own the fork. This will allow you to:
- Evolve the existing modules.
- Create your own modules.
- Sync from the upstream repository to get all the updates.
-
Use GitHub sources with refs to reference the modules. See an example below:
module "project" { source = "github.com/GoogleCloudPlatform/cloud-foundation-fabric//modules/project?ref=v35.0.0&depth=1" name = "my-project" billing_account = "123456-123456-123456" parent = "organizations/123456" }
Foundational modules
- Billing account
- Cloud Identity group
- Folder
- Service accounts
- Logging bucket
- Organization
- Project
- Projects (data source)
Process factories
Networking modules
- Address reservation
- Cloud Endpoints
- DNS
- DNS Response Policy
- Firewall policy
- External Application Load Balancer
- External Passthrough Network Load Balancer
- External Regional Application Load Balancer
- Internal Application Load Balancer
- Cross-region Internal Application Load Balancer
- Internal Passthrough Network Load Balancer
- Internal Proxy Network Load Balancer
- NAT
- Service Directory
- VPC
- VPC firewall
- VPC peering
- VPN dynamic
- VPN HA
- VPN static
Compute/Container
- VM/VM group
- MIG
- COS container (coredns/mysql/nva/onprem/squid)
- GKE autopilot cluster
- GKE standard cluster
- GKE hub
- GKE nodepool
- GCVE private cloud
Data
- AlloyDB
- Analytics Hub
- BigQuery connection
- BigQuery dataset
- Bigtable instance
- Biglake catalog
- Cloud SQL instance
- Data Catalog Policy Tag
- Data Catalog Tag
- Data Catalog Tag Template
- Dataform Repository
- Datafusion
- Dataplex
- Dataplex Aspect Types
- Dataplex DataScan
- Dataproc
- Firestore
- GCS
- Looker Core
- Pub/Sub
- Spanner instance
AI
Development
- API Gateway
- Apigee
- Artifact Registry
- Cloud Build V2 Connection
- Container Registry
- Cloud Source Repository
- Cloud Deploy
- Secure Source Manager instance
- Workstation cluster
Security
- Binauthz
- Certificate Authority Service (CAS)
- KMS
- SecretManager
- VPC Service Control
- Secure Web Proxy
- Certificate Manager