Replies: 1 comment
-
Hi @kollross, sorry for taking so long to answer, November was quire a busy month and and it just slipped my attention. For all practical purposes, managed records are records, and permissions are not an exception. Regarding the experimental "IPAM Coupling" feature, I released a new version containing quite a lot of fixes especially concerning exception handling and model-level operations for this, so probably it's best for you to re-test and open an issue should you find anything not working as it should (which is, to be honest, quite probable). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to figure out what permission knobs I need to turn to to allow non admin users to create DNS records for the "managed records" portion of the plugin.
Under the old way, I had created a custom field called "Company_org" which allowed me to limit that group to only view prefixes and vlan that also had that custom field applied (using constraints) . For IP addresses, same idea applied but I added the permission to edit along with view (they couldn't create IP's or delete them but could update the "DNS Name" field.
Obviously there is a lot more going on now with "managed records". I was able to craft a contrail to allow the zone to be selected from the list in the custom field. However saving produces a "You do not have permission to access this page.", even with full permissions granted to Netbox DNS -> zones and Netbox DNS -> records.
Logs looks like this: Note for IPAM->IP-Address I have it set to "can edit, view, change".
Beta Was this translation helpful? Give feedback.
All reactions