You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current provider and Go Client do not offer the ability to manage Authoritative DNS Zones in Infoblox. This would be very useful for teams that want to manage DNS in Infoblox alongside all their other infrastructure being created in Terraform.
The Authoritative Zone resource and fields are already present in the Infoblox NIOS API, they just aren't exposed in the Go Client or Terraform Provider yet.
Proposed Changes
Add a new schema for an infoblox_zone_auth resource that includes the relevant fields, and the requisite functions to create and manage the resource.
Example Usage
resource"infoblox_zone_auth""prod123_zone" {
fqdn="prod123.example.com"ns_group="Prod_NS_Group"restart_if_needed=truecomment="Managed by Terraform"soa_default_ttl=3600soa_expire=2419200soa_negative_ttl=900soa_refresh=10800soa_retry=3600
}
Related Work
To enable this feature in the provider, we've also submitted an Issue and PR to the infoblox-go-client to enable the relevant fields on Authoritative Zone resources.
Context
The current provider and Go Client do not offer the ability to manage Authoritative DNS Zones in Infoblox. This would be very useful for teams that want to manage DNS in Infoblox alongside all their other infrastructure being created in Terraform.
The Authoritative Zone resource and fields are already present in the Infoblox NIOS API, they just aren't exposed in the Go Client or Terraform Provider yet.
Proposed Changes
Add a new schema for an
infoblox_zone_auth
resource that includes the relevant fields, and the requisite functions to create and manage the resource.Example Usage
Related Work
To enable this feature in the provider, we've also submitted an Issue and PR to the infoblox-go-client to enable the relevant fields on Authoritative Zone resources.
The text was updated successfully, but these errors were encountered: