chore: Doc/release notes v2.9.0 (#464)

Author: Aish-sp

CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## [v2.9.0](https://github.com/infobloxopen/terraform-provider-infoblox/tree/v2.9.0) (2025-1-31)
+- New Resources:
+  - infoblox_dtc_lbdn
+  - infoblox_dtc_pool
+  - infoblox_dtc_server
+- New Datasources:
+  - infoblox_dtc_lbdn
+  - infoblox_dtc_pool
+  - infoblox_dtc_server
+
 ## [v2.8.0](https://github.com/infobloxopen/terraform-provider-infoblox/tree/v2.8.0) (2024-10-30)
 - New Feature: 
   - Support for Creating Objects with the Next Available IP Address and Next Available Network Obtained Using the Extensible Attribute Filter.

GETTING.md

@@ -12,7 +12,7 @@ Specify the plugin version in the .tf file as follows:
       required_providers {
         infoblox = {
           source = "infobloxopen/infoblox"
-          version = ">= 2.8.0"
+          version = ">= 2.9.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.8.0](https://github.com/infobloxopen/terraform-provider-infoblox/releases/tag/v2.8.0)
+The latest version of Infoblox provider is [v2.9.0](https://github.com/infobloxopen/terraform-provider-infoblox/releases/tag/v2.9.0)
 
 ## Provider Features
 
@@ -32,6 +32,9 @@ The provider plug-in has NIOS DDI resources represented as Terraform resources a
     * Association and disassociation of an IP address from a VM (`infoblox_ip_association`)
 * Zone Forward (`infoblox_zone_forward`)
 * Zone Delegated (`infoblox_zone_delegated`)
+* DTC LBDN (`infoblox_dtc_lbdn`)
+* DTC Pool (`infoblox_dtc_pool`)
+* DTC Server (`infoblox_dtc_server`)
 
 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.
@@ -57,6 +60,9 @@ DNS records and the `infoblox_ip_allocation` resources are supported with `ttl`
 * IPv6 Network Container (`infoblox_ipv6_network_container`)
 * Host-record (`infoblox_host_record`)
 * Zone Delegated (`infoblox_zone_delegated`)
+* DTC LBDN (`infoblox_dtc_lbdn`)
+* DTC Pool (`infoblox_dtc_pool`)
+* DTC Server (`infoblox_dtc_server`)
 
 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.

docs/index.md

@@ -13,11 +13,23 @@ Whether you intend to use the published plug-in or the customized version that y
     "Cloud API Owned": "List Type (Values True, False)"
 }
 ```
-You may add other extensible attributes that you want to use.
-- Create an extensible attribute by name Terraform Internal ID of type string in Infoblox NIOS as given in below curl command.
-```bash
-curl -k -u <user>:<password> -H "Content-Type: application/json" -X POST https://<Grid_IP>/wapi/v2.12.3/extensibleattributedef -d '{"name": "Terraform Internal ID", "flags": "CR", "type": "STRING", "comment": "Internal ID for Terraform Resource"}'
-```
+### **Creating the Terraform Internal ID Extensible Attribute**
+Create the Terraform Internal ID Extensible Attribute in NIOS using one of the following methods. Only a NIOS admin with superuser privileges can create extensible attributes in NIOS.
+- Create the extensible attribute manually in Infoblox NIOS Grid Manager. For steps, refer to the Adding Extensible Attributes topic in the [Infoblox NIOS Documentation](https://infoblox-docs.atlassian.net/wiki/spaces/ipamdriverterraform10draft/pages/17268877).
+    
+  If the user you want to manage is a cloud member, then enable the following option for the extensible attribute:
+  - In Grid Manager, on the **Administration tab > Extensible Attributes** tab, edit the extensible attribute.
+  - On the **Additional Properties** tab, enable **Allow cloud members to have the following access to this extensible attribute** and select **Read/Write (and disallow Write access from the GUI and the standard API)**.
+- Use the following cURL command to create the extensible attribute as a read-only attribute in NIOS:
+
+    ```bash
+    curl -k -u <user>:<password> -H "Content-Type: application/json" -X POST https://<Grid_IP>/wapi/v2.12.3/extensibleattributedef -d '{"name": "Terraform Internal ID", "flags": "CR", "type": "STRING", "comment": "Internal ID for Terraform Resource"}'
+    ```
+
+  - If the user you want to manage is a cloud member, then include the flag C for cloud API.
+  - If you are using multiple flags in the command, ensure that the flags are written in correct order. For more information about flags, refer to the Extensible Attribute Definition object in the [Infoblox WAPI Documentation](https://infoblox-docs.atlassian.net/wiki/spaces/ipamdriverterraform10draft/pages/17268877).
+
+- Enable IPAM Plug-In for Terraform to automatically create the extensible attribute by configuring the terraform Infoblox provider with credentials of a NIOS admin user with superuser privileges. For more information, see [Configure the Access Permissions](https://infoblox-docs.atlassian.net/wiki/spaces/ipamdriverterraform10draft/pages/17268877).
 
 > **Note:**
 >
@@ -46,7 +58,7 @@ terraform {
     required_providers {
         infoblox = {
             source  = "infobloxopen/infoblox"
-            version = ">= 2.8.0"
+            version = ">= 2.9.0"
         }
     }
 }
@@ -56,7 +68,7 @@ Configure the credentials required to access the NIOS Grid as environment variab
 
 
 ```bash
- # Using environment variable 
+ # Using environment variable
  $ export INFOBLOX_SERVER=<nios_ip-addr or nios_hostname>
  $ export INFOBLOX_USERNAME=<nios_username>
  $ export INFOBLOX_PASSWORD=<nios_password>
@@ -102,6 +114,9 @@ There are resources for the following objects, supported by the plugin:
 * Zone Forward (`infoblox_zone_forward`)
 * Host record (`infoblox_ip_allocation` / `infoblox_ip_association`)
 * Zone Delegated (`infoblox_zone_delegated`)
+* DTC LBDN (`infoblox_dtc_lbdn`)
+* DTC Pool (`infoblox_dtc_pool`)
+* DTC Server (`infoblox_dtc_server`)
 
 Network and network container resources have two versions: IPv4 and IPv6. In
 addition, there are two operations which are implemented as resources:
@@ -154,6 +169,9 @@ There are data sources for the following objects:
 * Zone Forward (`infoblox_zone_forward`)
 * Host Record (`infoblox_host_record`)
 * Zone Delegated (`infoblox_zone_delegated`)
+* DTC LBDN (`infoblox_dtc_lbdn`)
+* DTC Pool (`infoblox_dtc_pool`)
+* DTC Server (`infoblox_dtc_server`)
 
 !> From version 2.5.0, new feature filters are introduced. Now the data sources support to populate more than one
 matching NIOS objects.
@@ -288,7 +306,7 @@ import {
 ```
 #### Example for importing A-records from a zone
 ```hcl
-//import all A-records from the zone /example1.org 
+//import all A-records from the zone /example1.org
 data "infoblox_a_record" "data_arec" {
     filters = {
       zone = "example1.org "