Host record incorrectly has configured for DHCP set to true

[sandeep444033]

When creating a host recording using infoblox_ip_allocation the created record usage is DNS/DHCP. There doesn't appear to be a way to stop DHCP usage from being set. An effect of this is that grid services need to be restarted. Here is my resource config:

resource "infoblox_ip_allocation" "demo_allocation" {
  vm_name   = "test"
  cidr      = "10.x.x.x/24"
  tenant_id = "test"
  enable_dns = true
  # required for host record
  zone    = "test.com"
  dns_view = "default"
}

[somashekhar]

There are two things here,

1. infoblox_ip_allocation uses NIOS DHCP to allocate the next available IP from the given CIDR
2. The above allocated IP can be used to create a HOST record at IPAM or DNS ends.

We see it as a clean usage and we don't see a need of grid services restart. A bit more explanation of the issue faced would help us.

[sandeep444033]

@somashekhar,

Original intention of my use case here is, just to have a host record created for DNS usage, my DNS team do not want every record to be labelled as DHCP (they are good if it is a true DHCP record) as it creates performance issue on the appliances.

To give more insight, I am able to successfully create a host record with this provider, but when I query it, it says it is labeled for both DNS and DHCP, as opposed to my usage only for DNS.

I looked at the Infoblox API documentation and found out that enable_for_dhcp option to be passed as false, if I do not need DHCP usage type for my host record, but there is no way to date with Terraform Infoblox provider type to pass this attribute during host record creation (with infoblox_ip_allocation resource type) , which results a record to be dual usage type.

Please let me know if this clarifies.

[sandeep444033]

@somashekhar

This is the reply I got from my Infoblox admin when checking if the host record created by Terraform is good,

"Configuring DHCP does trigger a restart of DHCP services which in turn causes performance issues."

[somashekhar]

Requirement:
Create and use a Host Record only at DNS end. It should not be created at both DNS and DHCP end.

Hope we have got the requirement rightly.

[sandeep444033]

@somashekhar

Yes that exactly gets my requirement.

Can I have any timelines for this implementation?

[somashekhar]

Have conveyed the ask to our PM @saileshgiri . Probably he would be the right person to give details on timeline.

[sandeep444033]

@somashekhar / @saileshgiri

Any update on when this would be available?

[saileshgiri]

We'll release a new plugin version by next week. This issue is addressed in that

[sandeep444033]

@somashekhar

Is this implemented?

[somashekhar]

Yes. It was implemented in our version 2.0.1

[sandeep444033]

Thanks for the confirmation, @somashekhar.