Gcore Terraform Provider v2: rebuilt from the ground up

We're excited to announce the alpha release of Gcore Terraform Provider v2 — a complete rewrite of our Terraform provider, built for the way we build today.

This isn't an incremental update. It's a new foundation.

Why we rewrote it

As Gcore's platform has grown — across Cloud, AI infrastructure, CDN, DNS, and more — we wanted our Terraform provider to keep pace automatically rather than through manual updates. We set out to build something where the provider accurately reflects the API by construction, and where shipping updates is fast. v2 is the result.

What's new in v2

Auto-generated from our OpenAPI spec — and that changes everything. The v2 provider's schemas, documentation, and validation are generated directly from our API spec using industry-proven code generation tooling. This means the provider stays accurate and in sync with the API, and when we ship new API features, a matching Terraform update can follow quickly.

Built on the modern Terraform Plugin Framework. v2 is built on the current Terraform Plugin Framework, aligning us with where the ecosystem is heading and unlocking better performance and long-term maintainability.

One unified API client. v2 uses a single, unified Go client — gcore-go — keeping things consistent and easy to maintain across all resources.

Plural data sources. v2 adds plural data sources for most resources, making it much easier to query and manage groups of resources declaratively.

Import support. Almost all resources now support terraform import, enabling teams to bring existing Gcore infrastructure under Terraform management without starting from scratch.

What to know right now

v2 is in alpha. That means:

• Do not use it in production yet. Breaking changes between releases should be expected while the provider is in alpha.
• The existing provider (v0.*) remains fully supported. Documentation is still available and nothing is going away. We'll announce beta and General Availability milestones separately as v2 matures.

Both versions live in the same GitHub repository: the master branch holds the v0 provider, and the v2 branch holds the new one.

Migrating from v0 to v2

We know many of you have been using the v0 provider extensively — particularly for Cloud and AI workloads. We're committed to making the migration as smooth as possible.

Migration guidelines will be published as part of the v2 provider documentation. That said, we don't expect a fully automated migration path — Terraform configurations tend to be specific to how each team structures their infrastructure. For customers who want hands-on help, our Developer Experience team is happy to work through it with you directly, based on your specific setup. Don't hesitate to contact our support team via the customer portal.

Part of a bigger picture

This release is the next step in our broader push to improve developer experience across the Gcore platform. Earlier this year, we launched auto-generated SDKs in both Python and Go, covering all Gcore products. The new Terraform provider builds on that same foundation — one source of truth, the OpenAPI spec, powering everything.

What's next? A Gcore CLI. Watch this space.

Explore the Gcore Terraform Provider v2 →