---
title: 'GCP Terraform log collection: legacy modules deprecated'
description: The legacy push-based GCP Pub/Sub and storage Terraform modules are deprecated for new deployments. Use the pull-based GCP Logs integration.
url: https://coralogix.com/docs/user-guides/latest-updates/deprecations/gcp-terraform-v1-modules/
product: system
feature: Terraform Provider
feature_id: terraform-provider
feature_identifier: system/terraform-provider
last_updated: '2026-11-02'
---

# GCP Terraform log collection: legacy modules deprecated

**Published**: April 7, 2026

**Effective**: April 7, 2026

## Deprecation notice

Coralogix is deprecating the legacy push-based [GCP pub/sub Terraform module](https://coralogix.com/docs/integrations/gcp/gcp-pub/sub-terraform-module.md) and the Terraform deployment path documented in [GCP storage](https://coralogix.com/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/integrations/gcp/gcp-logs.md) integration instead.

## Why this is happening

Coralogix uses the managed, pull-based [GCP Logs](https://coralogix.com/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

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/integrations/gcp/gcp-pub/sub-terraform-module.md)
* [GCP storage](https://coralogix.com/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

### Use GCP Logs for new log-ingestion deployments

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

## 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/integrations/gcp/gcp-logs.md) integration.

## 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/integrations/gcp/gcp-logs.md).