Doc/Release notes for v2.10.0 (#490)

* Updated Documents
* Release Notes

Author: Aish-sp

CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [v2.10.0](https://github.com/infobloxopen/terraform-provider-infoblox/tree/v2.10.0) (2025-4-25)
+- New Resources:
+  - infoblox_alias_record
+  - infoblox_ns_record
+  - infoblox_ipv4_shared_network
+  - infoblox_ipv4_fixed_address
+  - infoblox_ipv4_range
+  - infoblox_ipv4_range_template
+- New Datasources:
+  - infoblox_alias_record
+  - infoblox_ns_record
+  - infoblox_ipv4_shared_network
+  - infoblox_ipv4_fixed_address
+  - infoblox_ipv4_range
+  - infoblox_ipv4_range_template
+
 ## [v2.9.0](https://github.com/infobloxopen/terraform-provider-infoblox/tree/v2.9.0) (2025-1-31)
 - Upgraded the base WAPI version to v2.12.3.
 - New Resources:

GETTING.md

@@ -12,7 +12,7 @@ Specify the plugin version in the .tf file as follows:
       required_providers {
         infoblox = {
           source = "infobloxopen/infoblox"
-          version = ">= 2.9.0"
+          version = ">= 2.10.0"
         }
       }
     }

README.md

@@ -7,7 +7,7 @@
 This is a provider plug-in for Terraform to manage Infoblox NIOS (Network Identity Operating System) resources using Terraform infrastructure as code solutions.
 The plug-in enables lifecycle management of Infoblox NIOS DDI resources.
 
-The latest version of Infoblox provider is [v2.9.0](https://github.com/infobloxopen/terraform-provider-infoblox/releases/tag/v2.9.0)
+The latest version of Infoblox provider is [v2.10.0](https://github.com/infobloxopen/terraform-provider-infoblox/releases/tag/v2.10.0)
 
 > **Note:** Plugin version **v2.9.0** includes an upgrade to the base WAPI version to **v2.12.3**.
 
@@ -37,6 +37,12 @@ The provider plug-in has NIOS DDI resources represented as Terraform resources a
 * DTC LBDN (`infoblox_dtc_lbdn`)
 * DTC Pool (`infoblox_dtc_pool`)
 * DTC Server (`infoblox_dtc_server`)
+* Alias-record (`infoblox_alias_record`)
+* NS-record (`infoblox_ns_record`)
+* IPV4 Shared Network (`infoblox_ipv4_shared_network`)
+* IPV4 Fixed Address (`infoblox_ipv4_fixed_address`)
+* IPV4 Range (`infoblox_ipv4_range`)
+* IPV4 Range Template (`infoblox_ipv4_range_template`)
 
 All of the above resources are supported with `comment` and `ext_attrs` fields.
 DNS records and the `infoblox_ip_allocation` resources are supported with `ttl` field.
@@ -65,6 +71,12 @@ DNS records and the `infoblox_ip_allocation` resources are supported with `ttl`
 * DTC LBDN (`infoblox_dtc_lbdn`)
 * DTC Pool (`infoblox_dtc_pool`)
 * DTC Server (`infoblox_dtc_server`)
+* Alias-record (`infoblox_alias_record`)
+* NS-record (`infoblox_ns_record`)
+* IPV4 Shared Network (`infoblox_ipv4_shared_network`)
+* IPV4 Fixed Address (`infoblox_ipv4_fixed_address`)
+* IPV4 Range (`infoblox_ipv4_range`)
+* IPV4 Range Template (`infoblox_ipv4_range_template`)
 
 All of the above data sources are supported with `comment` and `ext_attr` fields.
 Data source of DNS records are supported with `ttl` and `zone` fields.
@@ -128,6 +140,10 @@ The limitations of Infoblox IPAM Plug-In for Terraform are as follows:
 * When using the Terraform `import` block for a resource, a new Terraform internal ID is assigned to the resource when 
   the `terraform plan` command is run for the first time. If a subsequent `terraform apply` is aborted, the record will 
   still retain the `Terraform Internal ID` though the resource is not managed by Terraform.
+* The plug-in does not support retrieving information about IPv4 range and IPv4 range template objects by specifying the
+  member or ms_server field in the filter attribute of the object’s data source block.
+* When you update the DHCP options for a shared network, an IPv4 fixed address, an IPv4 range, or an IPv4 range template
+  object, the DHCP options show as re-ordering when the next terraform plan command runs.
 
 ## Best Practices
 

docs/data-sources/infoblox_ipv4_network.md

@@ -6,15 +6,21 @@ The data source for the network object allows you to get the following parameter
 * `cidr`: the network block which corresponds to the network, in CIDR notation. Example: `192.0.17.0/24`
 * `comment`: a description of the network. This is a regular comment. Example: `Untrusted network`.
 * `ext_attrs`: The set of extensible attributes, if any. The content is formatted as string of JSON map. Example: `"{\"Owner\":\"State Library\",\"Administrator\":\"unknown\"}"`.
-* `options`: An array of DHCP option structs that lists the DHCP options associated with the object.
+* `options`: An array of DHCP option structs that lists the DHCP options associated with the object. The description of the fields of `options` is as follows:
+    * `name`: The Name of the DHCP option. Example: `domain-name-servers`.
+    * `num`: The code of the DHCP option. Example: `6`.
+    * `value`: The value of the option. Example: `11.22.33.44`.
+    * `vendor_class`: The name of the space this DHCP option is associated to. Default value is `DHCP`.
+    * `use_option`:Only applies to special options that are displayed separately from other options and have a use flag. These options are `router`,
+      `router-templates`, `domain-name-servers`, `domain-name`, `broadcast-address`, `broadcast-address-offset`, `dhcp-lease-time`, and `dhcp6.name-servers`.
 ```terraform
 options {
-  name         = "dhcp-lease-time"
-  value        = "43200"
-  vendor_class = "DHCP"
-  num          = 51
-  use_option   = true
-}
+    name         = "dhcp-lease-time"
+    value        = "43200"
+    vendor_class = "DHCP"
+    num          = 51
+    use_option   = true
+  }
 ```
 * `utilization`: The network utilization in percentage. Example: `0`
 

docs/data-sources/infoblox_ipv4_range.md

@@ -1,6 +1,6 @@
 # Range Data Source
 
-Use the `infoblox_ipv4_range` data source to retrieve the following information for an Range if any, which is managed by a NIOS server:
+Use the `infoblox_ipv4_range` data source to retrieve the following information for an IPV4 Range if any, which is managed by a NIOS server:
 
 * `name`: specifies the display name. Example: `network-range`.
 * `comment`: comment for the range, maximum 256 characters. Example: `test range`.
@@ -34,6 +34,7 @@ options {
   * `name`: The name of the Grid member. Example: `infoblox.localdomain`.
   * `ipv4addr`: The IPv4 Address of the Grid Member. Example: `11.10.1.0`.
   * `ipv6addr`: The IPv6 address of the member. Example: `2403:8600:80cf:e10c:3a00::1192`.
+* `cloud_info`: Structure containing all cloud API related information for this object. Example: `"{\"authority_type\":\"GM\",\"delegated_scope\":\"NONE\",\"owned_by_adaptor\":false}"`
 
 Example for `member`:
 ```terraform

docs/data-sources/infoblox_ipv4_range_template.md

@@ -25,8 +25,8 @@ options {
 * `comment`: The description of the record. This is a regular comment. Example: `Temporary Ipv4 Shared Network`.
 * `ext_attrs`: The set of extensible attributes of the record, if any. The content is formatted as string of JSON map. Example: `"{\"Site\":"Nagoya"}"`
 * `server_association_type`: The type of server that is going to serve the range. Valid values are: `FAILOVER`, `MEMBER`, `MS_FAILOVER`, `MS_SERVER`, `NONE` .Example: `NONE`.
-* `failover_association`: The name of the failover association: the server in this failover association will serve the IPv4 range in case the main server is out of service. Example: `test.com`.
-* `ms_server`: The Microsoft server that will provide service for this range. `server_association_type` needs to be set to `MS_SERVER` if you want the server specified here to serve the range.
+* `failover_association`: The name of the failover association: the server in this failover association will serve the IPv4 range in case the main server is out of service. Example: `dhcp_failover`.
+* `ms_server`: The Microsoft server that will provide service for this range. `server_association_type` needs to be set to `MS_SERVER` if you want the server specified here to serve the range. Example: `10.23.23.2`.
 * `member`: The member that will provide service for this range. `server_association_type` needs to be set to `MEMBER` if you want the server specified here to serve the range. `member` has the following three fields `name`, `ipv4addr` and `ipv6addr`.The description of the fields of `member` is as follows:
   * `name`: The name of the Grid member. Example: `infoblox.localdomain`.
   * `ipv4addr`: The IPv4 Address of the Grid Member. Example: `11.10.1.0`.
@@ -41,7 +41,7 @@ member = {
   }
 ```
 
-For usage of filters, add the fields as keys and appropriate values to be passed to the keys like `name`, `view`, `zone`, `comment`, `target_name`, and `target_type`  corresponding to object.
+For usage of filters, add the fields as keys and appropriate values to be passed to the keys like `name`, `failover_association`, `comment`, and `server_association_type`  corresponding to object.
 From the below list of supported arguments for filters,  use only the searchable fields for retrieving the matching records.
 
 ### Supported Arguments for filters
@@ -95,7 +95,7 @@ resource "infoblox_ipv4_range_template" "range_template_record" {
     num = 6
     use_option = true
   }
-  member {
+  member = {
     ipv4addr = "10.197.81.146"
     ipv6addr = "2403:8600:80cf:e10c:3a00::1192"
     name = "infoblox.localdomain"

docs/data-sources/infoblox_ipv6_network.md

@@ -6,7 +6,22 @@ The data source for the network object allows you to get the following parameter
 * `cidr`: the network block which corresponds to the network, in CIDR notation. Example: `2002:1f93:0:4::/96`
 * `comment`: a description of the network. This is a regular comment. Example: `Untrusted network`.
 * `ext_attrs`: The set of extensible attributes, if any. The content is formatted as string of JSON map. Example: `"{\"Owner\":\"State Library\",\"Administrator\":\"unknown\"}"`.
-
+* `options`: An array of DHCP option structs that lists the DHCP options associated with the object. The description of the fields of `options` is as follows:
+    * `name`: The Name of the DHCP option. Example: `domain-name-servers`.
+    * `num`: The code of the DHCP option. Example: `6`.
+    * `value`: The value of the option. Example: `11.22.33.44`.
+    * `vendor_class`: The name of the space this DHCP option is associated to. Default value is `DHCP`.
+    * `use_option`:Only applies to special options that are displayed separately from other options and have a use flag. These options are `router`,
+      `router-templates`, `domain-name-servers`, `domain-name`, `broadcast-address`, `broadcast-address-offset`, `dhcp-lease-time`, and `dhcp6.name-servers`.
+```terraform
+options {
+    name         = "dhcp-lease-time"
+    value        = "43200"
+    vendor_class = "DHCP"
+    num          = 51
+    use_option   = true
+  }
+```
 
 To retrieve information about IPv6 network that match the specified filters, use the `filters` argument and specify the parameters mentioned in the below table. These are the searchable parameters of the corresponding object in Infoblox NIOS WAPI. If you do not specify any parameter, the data source retrieves information about all host records in the NIOS Grid.
 

docs/index.md

@@ -5,7 +5,7 @@
 Whether you intend to use the published plug-in or the customized version that you have built yourself, you must complete the following prerequisites:
 
 - Install and set up a physical or virtual Infoblox NIOS appliance and has necessary licenses installed. Configure the access permissions for Terraform to interact with NIOS Grid objects.
-- To use the Infoblox IPAM Plug-In for Terraform, you must either define the following extensible attributes or install the Cloud Network Automation license in the NIOS Grid, which adds the extensible attributes by default:
+- To use the Infoblox IPAM Plug-In for Terraform with a cloud user, you must either define the following extensible attributes or install the Cloud Network Automation license in the NIOS Grid, which adds the extensible attributes by default:
 ```json
 {
     "Tenant ID": "String Type",
@@ -58,7 +58,7 @@ terraform {
     required_providers {
         infoblox = {
             source  = "infobloxopen/infoblox"
-            version = ">= 2.9.0"
+            version = ">= 2.10.0"
         }
     }
 }
@@ -118,6 +118,12 @@ There are resources for the following objects, supported by the plugin:
 * DTC LBDN (`infoblox_dtc_lbdn`)
 * DTC Pool (`infoblox_dtc_pool`)
 * DTC Server (`infoblox_dtc_server`)
+* Alias-record (`infoblox_alias_record`)
+* NS-record (`infoblox_ns_record`)
+* IPV4 Shared Network (`infoblox_ipv4_shared_network`)
+* IPV4 Fixed Address (`infoblox_ipv4_fixed_address`)
+* IPV4 Range (`infoblox_ipv4_range`)
+* IPV4 Range Template (`infoblox_ipv4_range_template`)
 
 Network and network container resources have two versions: IPv4 and IPv6. In
 addition, there are two operations which are implemented as resources:
@@ -173,6 +179,12 @@ There are data sources for the following objects:
 * DTC LBDN (`infoblox_dtc_lbdn`)
 * DTC Pool (`infoblox_dtc_pool`)
 * DTC Server (`infoblox_dtc_server`)
+* Alias-record (`infoblox_alias_record`)
+* NS-record (`infoblox_ns_record`)
+* IPV4 Shared Network (`infoblox_ipv4_shared_network`)
+* IPV4 Fixed Address (`infoblox_ipv4_fixed_address`)
+* IPV4 Range (`infoblox_ipv4_range`)
+* IPV4 Range Template (`infoblox_ipv4_range_template`)
 
 !> From version 2.5.0, new feature filters are introduced. Now the data sources support to populate more than one
 matching NIOS objects.

docs/resources/infoblox_ipv4_fixed_address.md

@@ -35,6 +35,17 @@ options {
 ```
 * `use_options`: optional, Use option is a flag that indicates whether the options field are used or not. The default value is false. Example: `false`
 
+!> When configuring the options parameter, you must define the default option dhcp-lease-time to avoid the undesirable changes that can occur when the next terraform apply command runs. The sub parameters name, num, and value are required. An example block is as follows:
+```terraform
+options {
+  name         = "dhcp-lease-time"
+  value        = "43200"
+  vendor_class = "DHCP"
+  num          = 51
+  use_option   = false
+}
+```
+
 ## Example for Fixed Address Block 
 
 ```hcl

docs/resources/infoblox_ipv4_range.md

@@ -48,6 +48,18 @@ member = {
 }
 ```
 * `template` : optional, If set on creation, the range will be created according to the values specified in the named template. Example: `range_template`
+
+!> When configuring the options parameter, you must define the default option dhcp-lease-time to avoid the undesirable changes that can occur when the next terraform apply command runs. The sub parameters name, num, and value are required. An example block is as follows:
+```terraform
+options {
+  name         = "dhcp-lease-time"
+  value        = "43200"
+  vendor_class = "DHCP"
+  num          = 51
+  use_option   = false
+}
+```
+
 ### Examples of a Network Range Block
 ```hcl
 // creating a Network Range