-
Notifications
You must be signed in to change notification settings - Fork 12
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
Alternative netbox.netbox.nb_inventory_inventory #5
Comments
If I understood the netbox.netbox.nb_inventory right it is able to generate a dynamic inventory in a generic way. With your addition it would also be able to export the inventory to files. On the other hand the netbox-joined-inventory is part of a networking stack that is able to configure switches. It can take all VLAN, VXLAN, Anycast, MLAG , BGP data and more all from netbox. As all this joining is very specific to this networking stack I doubt that the more generic netbox.netbox.nb_inventory could replace the netbox-joined-inventory. |
Right. That is the thing I was not sure about, how difficult it would be to implement your use case with the generic inventory. From the data model and the implementation it looks like explicit IPAM access is not provided by Thanks again for sharing all this work! |
It looks to me that this script got deprecated by https://netbox-ansible-collection.readthedocs.io/en/latest/plugins/inventory/nb_inventory/netbox.netbox.nb_inventory_inventory.html. The reason I looked into netbox-joined-inventory was that it provides a nice way to generate inventory files that one can review. I have now tested a way to get a similar behavior with
netbox.netbox.nb_inventory
:ansible/inventory/netbox.yml
:ansible/refresh-netbox.yml
:ansible.cfg
:Makefile
:To refresh the cache, run
ansible-inventory -v --list -i ansible/refresh-netbox.yml
and then review the changes in~/.ansible/inventory_cache
ormake refresh-netbox
.You could also use
ansible-playbook --diff --check
in combination with manual cache refresh.What do you think?
The text was updated successfully, but these errors were encountered: