# GCP Terraform log collection: legacy modules deprecated

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Flatest-updates%2Fdeprecations%2Fgcp-terraform-v1-modules.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Flatest-updates%2Fdeprecations%2Fgcp-terraform-v1-modules.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

**Published**: April 7, 2026

**Effective**: April 7, 2026

## Deprecation notice[​](#deprecation-notice "Direct link to Deprecation notice")

Coralogix is deprecating the legacy push-based [GCP pub/sub Terraform module](https://coralogix.com/docs/docs/integrations/gcp/gcp-pub/sub-terraform-module/.md) and the Terraform deployment path documented in [GCP storage](https://coralogix.com/docs/docs/integrations/gcp/gcp-storage/.md) for **new deployments** effective April 7, 2026.

For new GCP log-ingestion deployments, use the pull-based [GCP Logs](https://coralogix.com/docs/docs/integrations/gcp/gcp-logs/.md) integration instead.

## Why this is happening[​](#why-this-is-happening "Direct link to Why this is happening")

Coralogix uses the managed, pull-based [GCP Logs](https://coralogix.com/docs/docs/integrations/gcp/gcp-logs/.md) integration for new GCP log-ingestion deployments. In that model, Coralogix reads from a GCP Pub/Sub pull subscription. It aligns better with the current Coralogix integration model and avoids continued investment in legacy Cloud Function-based, push-style Terraform collectors.

## What's affected[​](#whats-affected "Direct link to What's affected")

These legacy v1 Terraform module paths make up the older push-based collector path:

* `modules/pubsub`
* `modules/storage`

This includes the public documentation pages:

* [GCP pub/sub Terraform module](https://coralogix.com/docs/docs/integrations/gcp/gcp-pub/sub-terraform-module/.md)
* [GCP storage](https://coralogix.com/docs/docs/integrations/gcp/gcp-storage/.md)

Existing deployments that already use these module paths can continue to reference the legacy documentation for maintenance, but these modules are not the starting point for new implementations.

## What you need to do[​](#what-you-need-to-do "Direct link to What you need to do")

### Use GCP Logs for new log-ingestion deployments[​](#use-gcp-logs-for-new-log-ingestion-deployments "Direct link to Use GCP Logs for new log-ingestion deployments")

For new GCP log collection setups, follow the [GCP Logs](https://coralogix.com/docs/docs/integrations/gcp/gcp-logs/.md) integration guide. This is the pull-based replacement path for new deployments.

## What changes after April 7, 2026?[​](#what-changes-after-april-7-2026 "Direct link to What changes after April 7, 2026?")

* The legacy v1 GCP Terraform module paths remain available for existing maintenance workflows, but Coralogix does not support them for new deployments.
* New GCP log-ingestion guidance from Coralogix points customers to the pull-based [GCP Logs](https://coralogix.com/docs/docs/integrations/gcp/gcp-logs/.md) integration.

## Need help?[​](#need-help "Direct link to Need help?")

Reach out through our 24/7 in-app support or contact your Technical Account Manager if you need help migrating from the legacy v1 modules to [GCP Logs](https://coralogix.com/docs/docs/integrations/gcp/gcp-logs/.md).