nutanix/terraform-provider-nutanix

Terraform Nutanix Provider

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Added to GitGenius on June 19th, 2026
Created on October 9th, 2018
Open Issues & Pull Requests: 195 (+0)
GitHub issues: Enabled
Number of forks: 139
Total Stargazers: 133 (+0)
Total Subscribers: 20 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.7 days
Mean response time: 106.1 days
90th percentile: 347.9 days
Tracked items: 284

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 82% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "2.4.0" is answered fastest, typically in under an hour, while "2.0" waits about 12 months. 59% of tracked open issues have had no activity in three months. Only 7% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 121
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 419 days
Stale 30+ days: 118
Stale 90+ days: 86

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • 2.3.0 (43)
  • feature (35)
  • 2.5.0 (34)
  • 2.0 (29)
  • 2.4.1 (17)
  • needs-triaging (12)
  • 2.3.1 (10)
  • 2.4.0 (10)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

The terraform-provider-nutanix repository is a Terraform provider plugin written in Go that enables infrastructure as code management of Nutanix Cloud Platform resources. The provider allows users to define, provision, and manage Nutanix infrastructure through Terraform configurations, using Prism Central as the endpoint for API interactions. The repository is maintained by Nutanix and serves as the official integration point between Terraform and Nutanix environments.

The provider supports a comprehensive range of resources and data sources across multiple Nutanix service domains. Version 2.4.2, the latest release, introduces Network Functions for service chaining and traffic forwarding, Entity Groups for microsegmentation use cases, IAM entities management, and VM Affinity Policies for governing virtual machine placement across hosts. The provider also supports virtual machine management, cluster operations, networking configuration including VPCs and subnets, security policies, object storage, database management through Nutanix Database Service, and Kubernetes cluster provisioning through Nutanix Kubernetes Engine.

Recent enhancements in v2.4.2 include support for deploying and updating virtual machines from OVA images, expanded Foundational Networking Services capabilities with global scope and subnet-based objects, metadata support on subnet resources, and alternative authentication methods using API keys and custom headers alongside traditional username and password authentication. The provider requires Terraform 0.12 or later and Go 1.17 or higher for building, and utilizes Terraform SDKv2 from release 1.3.0 onward.

The provider maintains broad compatibility across Nutanix versions, with version 2.4.2 supporting AOS 7.5 and 7.5.1 alongside Prism Central 7.5 and later. The compatibility matrix extends back through multiple major versions, supporting environments ranging from AOS 5.18 through current releases. Configuration flexibility is provided through multiple authentication mechanisms, including username and password credentials, API keys, custom HTTP headers for specialized network environments, and configurable endpoints and ports.

The repository includes example Terraform configurations demonstrating provider usage and maintains a modules directory containing pre-built Terraform modules based on the provider. Bug fixes in recent releases address issues including ETag mismatch errors during VM power operations, subnet update failures, VPC external routable prefix limitations, security policy creation defaults, object store functionality, and guest customization handling that previously triggered unnecessary resource recreation.