---
title: "Resources and Data Sources Supported by Infoblox IPAM Plug-In for Terraform"
canonical: "https://docs.infoblox.com/space/ipamdriverterraform/53154076/Resources%20and%20Data%20Sources%20Supported%20by%20Infoblox%20IPAM%20Plug-In%20for%20Terraform"
format: markdown
---
<span style="color: #000000">A Terraform resource constitutes a resource block that describes one or more NIOS Grid objects such as a network container and network. A Terraform data source allows data to be fetched or computed for use elsewhere in the Terraform configuration. With data sources, Terraform configuration is built on information defined outside of Terraform, or defined by a separate Terraform configuration.</span>

<span style="color: #000000">To perform a fetch, create, read, update, or delete operation on a NIOS object, you must define the appropriate resource or the data source block in the Terraform configuration (.tf) file. </span>Consider the following points when working with resources and data sources:

> ⚠️ <span style="color: #172B4D">**Note**</span>
> ⚠️ 
> ⚠️ - <span style="color: #172B4D">Infoblox recommends that you manage all resources supported by IPAM Plug-In for Terraform from Terraform only. Modifying a resource outside of Terraform may result in unexpected behavior.</span>
> ⚠️ - If you need to manage a large number of resources, Infoblox recommends that you manage them across multiple workspaces instead of using a single state file to manage all resources. For more information, see *[Managing Workspaces](https://developer.hashicorp.com/terraform/cli/workspaces)* and *[Structuring Terraform Configuration](https://www.hashicorp.com/blog/structuring-hashicorp-terraform-configuration-for-production)*.

- <span style="color: #000000">Network container and network resources are available in IPv4 and IPv6 versions.</span>
- <span style="color: #000000">IP address allocation and IP address association with a network host are implemented as resources such as VMs in a cloud environment. These resources are available in IPv4 and IPv6 versions.</span>
- <span style="color: #000000">Currently, the IPAM Plug-In for Terraform does not support creating a DNS zone. Therefore, to work with DNS records, you must ensure that appropriate DNS zones have been created in NIOS.</span>
- <span style="color: #000000">Every resource has the following common attributes that are optional:</span>
  - `comment`<span style="color: #000000"> is the text that describes the resource. If a value is not specified, an empty string is used as the default value.</span>
  - `ext_attrs`<span style="color: #000000"> is a set of NIOS extensible attributes attached to the resource being configured. </span><span style="color: #000000">If a value is not specified, an empty string is used as the default value</span><span style="color: #000000">.</span>
- <span style="color: #000000">All resources related to DNS have </span>`ttl`<span style="color: #000000"> as a common parameter, which is optional. It is the time interval during which the data is cached in the DNS server before it is updated.</span>  
<span style="color: #000000">If you do not configure the </span>`ttl`<span style="color: #000000"> parameter for a record, the TTL value is implicitly inherited from the zone the record belongs to. However, the output shows the </span>`ttl`<span style="color: #000000"> value as </span>`-2147483648`<span style="color: #000000">, which can be ignored.</span>
- The data source block that you define for a NIOS object includes the `filters` argument that allows you to specify the parameters that the corresponding object in Infoblox WAPI supports.
- When you specify extensible attributes filters in a data source block, you must use the following format:  
`"*<extensible_attribute_key>"="<value>"`.

<span style="color: #000000">The following topics detail the resources and data sources </span><span style="color: #000000">supported by Infoblox </span><span style="color: #000000">IPAM Plug-In version 2.7.0 for Terraform</span><span style="color: #000000"> and include appropriate examples of blocks that must be defined in the configuration file:</span>

> Macro (children)