Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Authoritative Zone resource #237

Closed
bsmithtm opened this issue Sep 13, 2022 · 3 comments
Closed

Add Authoritative Zone resource #237

bsmithtm opened this issue Sep 13, 2022 · 3 comments

Comments

@bsmithtm
Copy link

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

resource "infoblox_zone_auth" "prod123_zone" {
  fqdn              = "prod123.example.com"
  ns_group          = "Prod_NS_Group"
  restart_if_needed = true
  comment           = "Managed by Terraform"
  soa_default_ttl   = 3600
  soa_expire        = 2419200
  soa_negative_ttl  = 900
  soa_refresh       = 10800
  soa_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.

@dmpe
Copy link

dmpe commented Oct 19, 2023

Yes please. that would be indeed very much welcome.

@dmpe
Copy link

dmpe commented Oct 19, 2023

I think this can be closed due to recently merging this PR: #317.

@JkhatriInfobox
Copy link
Collaborator

As it is already merged as in PR #317, Hence closing the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants