Terraform provider plugin to integrate with Nutanix Enterprise Cloud
NOTE: The latest version of the Nutanix provider is v1.9.5
Modules based on Terraform Nutanix Provider can be found here : Modules
| Master | Develop |
|---|---|
 |
 |
Terraform Nutanix Provider leverages the community-supported model. See Open Source Support for more information about its support policy.
Nutanix is taking an inclusive approach to developing this new feature and welcomes customer feedback. Please see our development project on GitHub (you're here!), comment on requirements, design, code, and/or feel free to join us on Slack. Instructions on commenting, contributing, and joining our community Slack channel are all located within our GitHub Readme.
For a slack invite, please contact [email protected] from your business email address, and we'll add you.
The Terraform Nutanix provider is designed to work with Nutanix Prism Central and Standalone Foundation, such that you can manage one or more Prism Element clusters at scale. AOS/PC 5.6.0 or higher is required, as this Provider makes exclusive use of the v3 APIs. It also consists components to work with Foundation to performing node imaging and related activities.
For the 1.2.0 release of the provider it will have an N-1 compatibility with the Prism Central APIs. This provider was tested against Prism Central versions 2020.9 and 2020.11, as well as AOS version 5.18 and 5.19
For the 1.3.0 release of the provider it will have N-2 compatibility with the Prism Central APIs. This release was tested against Prism Central versions pc.2021.9.0.4, pc.2021.8.0.1 and pc.2021.7.
For the 1.4.0 & 1.4.1 release of the provider it will have N-2 compatibility with the Prism Central APIs. This release was tested against Prism Central versions pc2022.1 pc.2021.9.0.4 and pc.2021.8.0.1.
For the 1.5.0 release of the provider it will have N-2 compatibility with the Prism Central APIs. This release was tested against Prism Central versions pc2022.1.0.2 pc.2021.9.0.4 and pc.2021.8.0.1.
For the 1.6.1 release of the provider it will have N-2 compatibility with the Prism Central APIs. This release was tested against Prism Central versions pc2022.4 pc2022.1.0.2 and pc2021.9.0.4.
For the 1.7.0 release of the provider it will have N-2 compatibility with the Prism Central APIs. This release was tested against Prism Central versions pc2022.6, pc2022.4 and pc2022.1.0.2.
For the 1.7.1 release of the provider it will have N-2 compatibility with the Prism Central APIs. This release was tested against Prism Central versions pc2022.6, pc2022.4.0.1 and pc2022.1.0.2.
For the 1.9.0 release of the provider it will have N-1 compatibility with the Prism Central APIs. This release was tested against Prism Central versions pc2022.9 and pc2023.1.0.1.
For the 1.9.4 release of the provider it will have N-2 compatibility with the Prism Central APIs. This release was tested against Prism Central versions pc2023.3, pc2023.1.0.2 and pc2023.1.0.1.
With v1.6.1 release of flow networking feature in provider, IAMv2 setups would be mandate. Also, there is known issue for access_control_policies resource where update would be failing. We are continuously tracking the issue internally.
with v1.7.0 release of user groups feature in provider, pc version should be minimum 2022.1 to support organisational and saml user group.
With v1.7.1 release of project internal in provider is supported. Note to use this, set "use_project_internal" to true. It also enables the ACP mapping with projects.
For the 1.5.0-beta release of the provider it will have N-1 compatibility with the Foundation. This release was tested against Foundation versions v5.2 and v5.1.1
For the 1.5.0 release of the provider it will have N-1 compatibility with the Foundation. This release was tested against Foundation versions v5.2 and v5.1.1
Foundation based examples : https://github.com/nutanix/terraform-provider-nutanix/blob/master/examples/foundation/
Foundation based modules & examples : https://github.com/nutanix/terraform-provider-nutanix/blob/master/modules/foundation/
For the 1.5.0-beta.2 release of the provider it will have N-1 compatibility with the Foundation Central. This release was tested with v1.2 and v1.3 Foundation Central versions.
For the 1.5.0 release of the provider it will have N-1 compatibility with the Foundation Central. This release was tested with v1.2 and v1.3 Foundation Central versions.
Foundation Central based examples : https://github.com/nutanix/terraform-provider-nutanix/blob/master/examples/foundationCentral/
Foundation Central based modules and examples : Foundation based modules & examples : https://github.com/nutanix/terraform-provider-nutanix/blob/master/modules/foundationCentral/
For the 1.8.0-beta.1 release of the provider, it will have N-1 compatibility with the Nutanix database service. This release was tested with v2.4 and v2.4.1 versions.
For the 1.8.0-beta.2 release of the provider, it will have N-2 compatibilty with the Nutanix Database Service. This release was tested with v2.5.1.1 , v2.5.0.2 and v2.4.1
For the 1.8.0 release of the provider, it will have N-2 compatibility with the Nutanix database service. This release was tested with v2.5.1.1, v2.5.1 and v2.5 versions.
For the 1.8.1 release of the provider, it will have N-2 compatibility with the Nutanix database service. This release was tested with v2.5.1.1, v2.5.1 and v2.5 versions.
For the 1.9.5 release of the provider, it will have N-2 compatibility with the Nutanix database service. This release was tested with v2.5.1.1, v2.5.1 and v2.5 versions.
Note: For NDB related modules, only postgress database type is qualified and officially supported. Older versions of NDB may not support some resources.
Checkout example : https://github.com/nutanix/terraform-provider-nutanix/blob/master/examples/ndb/
See the Examples folder for a handful of main.tf demos as well as some pre-compiled binaries.
We'll be refreshing these examples and binaries as we work through tech preview.
Long term, once this is upstream, no pre-compiled binaries will be needed, as terraform will automatically download on use.
The following keys can be used to configure the provider.
- endpoint - (Required) IP address for the Nutanix Prism Central.
- username - (Required) Username for Nutanix Prism Central. Could be local cluster auth (e.g.
auth) or directory auth. - password - (Required) Password for the provided username.
- port - (Optional) Port for the Nutanix Prism Central. Default port is 9440.
- insecure - (Optional) Explicitly allow the provider to perform insecure SSL requests. If omitted, default value is false.
- wait_timeout - (optional) Set if you know that the creation o update of a resource may take long time (minutes).
provider "nutanix" {
username = "admin"
password = "myPassword"
port = 9440
endpoint = "10.36.7.201"
insecure = true
wait_timeout = 10
}The following keys can be used to configure the provider.
- endpoint - (Optional) IP address for the Nutanix Prism Central.
- username - (Optional) Username for Nutanix Prism Central. Could be local cluster auth (e.g.
auth) or directory auth. - password - (Optional) Password for the provided username.
- port - (Optional) Port for the Nutanix Prism Central. Default port is 9440.
- insecure - (Optional) Explicitly allow the provider to perform insecure SSL requests. If omitted, default value is false.
- wait_timeout - (optional) Set if you know that the creation or update of a resource may take long time (minutes).
- foundation_endpoint - (optional) IP address of foundation vm.
- foundation_port - (optional) Port of foundation vm. Default port is 8000.
provider "nutanix" {
username = "admin"
password = "myPassword"
port = 9440
endpoint = "10.36.7.201"
insecure = true
wait_timeout = 10
foundation_endpoint = "10.xx.xx.xx"
foundation_port = 8000
}- ndb_username - (Optional) Username of Nutanix Database Service server
- ndb_password - (Optional) Password of Nutanix Database Service server
- ndb_endpoint - (Optional) IP of Nutanix Database Service server
provider "nutanix" {
ndb_username = var.ndb_username
ndb_password = var.ndb_password
ndb_endpoint = var.ndb_endpoint
}From foundation getting released in 1.5.0-beta, provider configuration will accomodate prism central and foundation apis connection details. It will show warnings for disabled api connections as per the attributes given in provider configuration in above mentioned format. The below are the required attributes for corresponding provider componenets :
- endpoint, username and password are required fields for using Prism Central & Karbon based resources and data sources
- foundation_endpoint is required field for using Foundation based resources and data sources
- ndb_username, ndb_password and ndb_endpoint are required fields for using NDB based resources and data sources
- nutanix_access_control_policy
- nutanix_category_key
- nutanix_category_value
- nutanix_image
- nutanix_karbon_cluster
- nutanix_karbon_private_registry
- nutanix_network_security_rule
- nutanix_project
- nutanix_protection_rule
- nutanix_recovery_plan
- nutanix_role
- nutanix_subnet
- nutanix_user
- nutanix_virtual_machine
- nutanix_service_group
- nutanix_address_group
- nutanix_foundation_image_nodes
- nutanix_foundation_ipmi_config
- nutanix_foundation_image
- nutanix_foundation_central_api_keys
- nutanix_foundation_central_image_cluster
- nutanix_vpc
- nutanix_pbr
- nutanix_static_routes
- nutanix_floating_ip
- nutanix_user_groups
- nutanix_ndb_database
- nutanix_ndb_authorize_dbserver
- nutanix_ndb_clone
- nutanix_ndb_database_restore
- nutanix_ndb_database_scale
- nutanix_ndb_database_snapshot
- nutanix_ndb_linked_databases
- nutanix_ndb_log_catchups
- nutanix_ndb_profile
- nutanix_ndb_register_database
- nutanix_ndb_sla
- nutanix_ndb_software_version_profile
- nutanix_ndb_tms_cluster
- nutanix_ndb_tag
- nutanix_ndb_dbserver_vm
- nutanix_ndb_register_dbserver
- nutanix_ndb_clone_refresh
- nutanix_ndb_network
- nutanix_ndb_stretched_vlan
- nutanix_ndb_cluster
- nutanix_ndb_maintenance_task
- nutanix_ndb_maintenance_window
- nutanix_karbon_worker_nodepool
- nutanix_access_control_policies
- nutanix_access_control_policy
- nutanix_category_key
- nutanix_cluster
- nutanix_clusters
- nutanix_host
- nutanix_hosts
- nutanix_image
- nutanix_karbon_cluster_kubeconfig
- nutanix_karbon_cluster_ssh
- nutanix_karbon_cluster
- nutanix_karbon_clusters
- nutanix_karbon_private_registries
- nutanix_karbon_private_registry
- nutanix_network_security_rule
- nutanix_permission
- nutanix_permissions
- nutanix_project
- nutanix_projects
- nutanix_role
- nutanix_roles
- nutanix_subnet
- nutanix_subnets
- nutanix_user_group
- nutanix_user_groups
- nutanix_user
- nutanix_users
- nutanix_virtual_machine
- nutanix_protection_rule
- nutanix_protection_rules
- nutanix_recovery_plan
- nutanix_recovery_plans
- nutanix_address_groups
- nutanix_address_group
- nutanix_foundation_discover_nodes
- nutanix_foundation_node_network_details
- nutanix_foundation_nos_packages
- nutanix_foundation_hypervisor_isos
- nutanix_foundation_central_api_keys
- nutanix_foundation_central_list_api_keys
- nutanix_foundation_central_imaged_nodes_list
- nutanix_foundation_central_imaged_clusters_list
- nutanix_foundation_central_cluster_details
- nutanix_foundation_central_imaged_node_details
- nutanix_vpc
- nutanix_vpcs
- nutanix_pbr
- nutanix_pbrs
- nutanix_floating_ip
- nutanix_floating_ips
- nutanix_static_routes
- nutanix_ndb_cluster
- nutanix_ndb_clusters
- nutanix_ndb_database
- nutanix_ndb_databases
- nutanix_ndb_profile
- nutanix_ndb_profiles
- nutanix_ndb_sla
- nutanix_ndb_slas
- nutanix_ndb_clone
- nutanix_ndb_clones
- nutanix_ndb_snapshot
- nutanix_ndb_snapshots
- nutanix_ndb_tms_capability
- nutanix_ndb_time_machine
- nutanix_ndb_time_machines
- nutanix_ndb_dbserver
- nutanix_ndb_dbservers
- nutanix_ndb_tag
- nutanix_ndb_tags
- nutanix_ndb_network
- nutanix_ndb_networks
- nutanix_ndb_maintenance_window
- nutanix_ndb_maintenance_windows
- nutanix_ndb_network_available_ips
The Nutanix Provider for Terraform is the work of many contributors. We appreciate your help!