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

IPAM Coupling #74

Merged
merged 22 commits into from
Oct 17, 2023
Merged

IPAM Coupling #74

merged 22 commits into from
Oct 17, 2023

Conversation

peteeckel
Copy link
Owner

Integrate the work of @jean1 and a few small changes and enhancements.

jean1 and others added 22 commits October 16, 2023 21:36
* Introduce an experimental IPAM-DNS coupling feature

Two new custom fields are added on IP Address :
- name
- zone

Through a middleware and signals, all IP Address creation and modification
are intercepted. Using the new custom fields, the corresponding DNS record
is created, modified or deleted accordingly.

Permission on DNS records are enforced.

The IP address "dns_name" field is also updated.
* The original names 'name' and 'zone' are very generic. Given that the CF names
  are global within NetBox, they were renamed so they don't clash with other field
  names so easily
* Simplified the query for the required CFs
* Modified the log message to be a one-liner instead of four lines, which makes it
  hard to parse log messages automatically
* 'Related DNS Address Recordspanes' and 'Related DNS Pointer Records' panes in
   the ipam.IPAddress detail view now use records from 'ipam_coupling'
* 'Related DNS Pointer Zones' pane in the ipam.IPPrefix view was removed
@peteeckel peteeckel merged commit f22557b into main Oct 17, 2023
12 checks passed
@peteeckel peteeckel deleted the feature/ipam-coupling branch October 17, 2023 09:20
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 this pull request may close these issues.

2 participants