GCP Terraform log collection: legacy modules deprecated

Open in ChatGPTOpen in Claude

Published: April 7, 2026

Effective: April 7, 2026

Deprecation notice

Coralogix is deprecating the legacy push-based GCP pub/sub Terraform module and the Terraform deployment path documented in GCP storage for new deployments effective April 7, 2026.

For new GCP log-ingestion deployments, use the pull-based GCP Logs integration instead.

Why this is happening

Coralogix uses the managed, pull-based GCP Logs 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
• GCP storage

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 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 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.