Neon Terraform providers

The following is a list of community-created Terraform providers for managing Neon Postgres platform resources.

• Terraform Provider Neon — Maintainer: Dmitry Kisler (sponsored by Neon)

  • GitHub repository
  • Terraform Registry
  • Terraform Registry Documentation

• Terraform Neon Provider — Maintainer: Pavan Kumar Sunkara

  • GitHub repository
  • Terraform Registry
  • Terraform Registry Documentation

Important usage notes

• Upgrades: When using terraform init -upgrade to update a custom Terraform provider, be aware that changes in the provider’s schema or defaults can lead to unintended resource replacements. This may occur when certain attributes are altered or reset. For example, fields previously set to specific values might be reset to null, forcing the replacement of the entire resource.

  To avoid unintended resource replacements which can result in data loss:

  • Review the provider’s changelog for any breaking changes that might affect your resources before upgrading to a new version.
  • For CI pipelines and auto-approved pull requests, only use terraform init. Running terraform init -upgrade should be done manually followed by plan reviews.
  • Run terraform plan before applying any changes to detect potential differences and review the behavior of resource updates.
  • Use lifecycle protections on critical resources to ensure they're not recreated unintentionally.
  • Explicitly define all critical resource parameters in your Terraform configurations, even if they had defaults previously.
  • On Neon paid plans, you can enable branch protection to prevent unintended deletion of branches and projects. To learn more, see Protected branches.

Resources

• Terraform Documentation
• Initialize Terraform configuration
• Terraform plan command