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 Zone API #8

Open
Avarei opened this issue Jun 4, 2024 · 4 comments
Open

Add Zone API #8

Avarei opened this issue Jun 4, 2024 · 4 comments

Comments

@Avarei
Copy link

Avarei commented Jun 4, 2024

I would like to be able to manage DNS Zones in this provider.

This API should allow configuration of

  • FQDN
  • SOA fields
  • TSIG Keys
    • Name
    • Algorithm
    • Secret
  • Comment
  • Restart if Needed
  • View
  • Ext Attrs
  • NS Group

I would be happy contribute to this.

@Avarei
Copy link
Author

Avarei commented Jun 4, 2024

Currently this functionality is not implemented in the official go client: infobloxopen/infoblox-go-client#185
Since the issue appears stale and the ability to do contributions limited, due to auto-gen tools not being open source I expect that we would have to do our own implementation.

@stevendborrelli
Copy link
Collaborator

I think it would be a great contribution. What would be your preferred approach?

@stevendborrelli
Copy link
Collaborator

Was this implemented in the upstream provider? infobloxopen/terraform-provider-infoblox#317

@Avarei
Copy link
Author

Avarei commented Jun 8, 2024

Your absolutely right. For some reason I missed this, and I also just found out that the autogenerated go client does actually seem to have all of the ZoneAuth fields the Infoblox API provides...
I have no idea how I missed all of this...

The only thing missing from my wishlist would be TSIG Key support.
Though since the client supports all of that. this should be a minor addition.

While I am more familiar with Crossplane Provider Development, this Contribution now seems more managebal for me to contribute directly upstream.

Would this make maintainance overall easier for you or are upstream changes in CRDs challenging with Upjet?
I would be open for either way.

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

No branches or pull requests

2 participants