AI NewsInfrastructureAnnouncement

Neon takes over the community Terraform provider and calls it official

Neon adopted the community Terraform provider and moved secrets out of the state file.

AI News

Editorial2 min read

LinkedInX
Reveneau illustration standing in for a Neon blog hero on Terraform

Why it mattersA team that already used kislerdm/neon can replace the provider in one command. The new build keeps role passwords out of terraform.tfstate.

A role password written into terraform.tfstate is a leak waiting for the next person who clones the repository. Neon's new provider stops it by passing the credential to whichever resource needs it, then forgetting it.

Neon published the official Terraform provider this week. The code lives under neondatabase/neon on the Terraform Registry. A general release is planned within one to two weeks. The current build is v0.19.0-beta.4.

What changed about the provider

The community provider kislerdm/neon has been the way to drive Neon from Terraform for about three years. Dmitry Kisler started it and ran it alone. Neon says the community build has been downloaded nearly two million times. Of that total, 1.78 million came in the last twelve months.

Kisler, Neon engineer Andre Landgraf and platform engineer Justin Frye now maintain the official provider together. The last community release was v0.18.0.

The new build covers more of the Neon product. The list adds functions and triggers. It adds object storage buckets and bucket objects. It adds Auth with trusted domains and OAuth providers. It adds the Data API, snapshots, custom branch domains, spending limits, and member roles at the project and organisation level.

Ephemeral resources keep credentials out of the state file

Neon says that with the old provider "a role password or connection URI ended up in terraform.tfstate". The new provider marks those values as ephemeral. Terraform reads them during the run and does not write them to state.

This matters for anyone who checks state into a shared store or into source control by accident. A compromised state file no longer hands over a working Postgres role.

How a team moves across

A team that already runs the community provider changes the source address. Then it runs terraform state replace-provider, with the old and new addresses in order. Neon's post flags two shape changes in the new provider. Some nested blocks are now attributes. Some string booleans are now real booleans. A plan after the swap will show these changes.

For a team buying this

Moving to the official provider trades one risk for another. Secrets leave the state file, which is a real win. The build is still in beta. The shape changes on upgrade day give a team one more diff to read. A careful team runs the swap in a staging workspace first. The plan should show only the shape change, with no drift. Then the same two commands run in production. The reader with staging to spare and an ephemeral guarantee to gain is the team this release is for.

Source

Andre Landgraf, Dmitry Kisler and Justin Frye, "The Neon Terraform provider is now official," Neon. The download totals are Neon's own figures.

SourceNeon

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX
Start a project