-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Enable CSV export for organizational objects (device roles, VLAN groups, etc.) #1714
Comments
Support for CSV import of device roles was introduced in NetBox v2.2.0. Device roles can be exported via the API; I don't think there's much value in adding CSV export for them. |
I'd use it for migrating easily between staging/production. On another note, the CSV import button is only present in the menu, but not on the |
To migrate between servers easiest would be to just dump and restore the database instead of one by one export and import. But that's of course only the way I see it. |
Just so I understand, are you running separate instances of NetBox for staging and production? Or what do you mean?
Yeah we should add those. I'll open a separate bug for that. |
@esajo I don't want to overwrite any (other) data that is already on the production instance.
Yes. Two instances. Plus devs usually spin up a local Docker-based instance for developing integrations. |
I'd like to see this feature as well. I'm doing the same thing as @cimnine is, my development boxes are based off of docker, which get thrown away frequently, so allowing a mass export would be very beneficial instead. I was able to use the API to export the |
So, this FR is really more for CSV-based export of all organizational objects, not just device roles, right? |
Thanks! |
Did a lot of cleanup around CSV import/export. Still want to add some tests specifically for it. |
Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation
Environment
Description
It'd be nice to export/import device roles the same way as device types.
The text was updated successfully, but these errors were encountered: