-
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
Device type exports: unclear which is CSV and which is YAML #8082
Comments
The "current view" option exports exactly that: the current table view (as CSV). This is consistent across all models, and YAML is not supported for this function. In contrast, "all data" exports all data, not just what has been included on the table. The only thing different about devices types is that "all data" exports as YAML rather than CSV (to include the associated component templates of each object). Additionally, selecting objects in the table has no bearing on the export function. The checkboxes are used only for the bulk operations listed under the table.
This seems like a pretty niche feature, but you're welcome to submit a feature request for it. Bear in mind it would need to be implemented for every relevant model in NetBox for consistency (not just device types).
This would also need to be a separate feature request. |
NetBox version
v3.1.1
Python version
3.8
Steps to Reproduce
Expected Behavior
Either it should export consistently as YAML; or the two different export modes should be clearly labelled as "CSV" and "YAML".
Observed Behavior
"Export > Current View" gives you
netbox_device types.csv
, in CSV format, with all the devices listed (not just the checked one)"Export > All Data" gives you a
netbox_device types.yaml
, a multi-document YAML file with all the devices listed (not just the checked one)What I was actually trying to do was to export the YAML definition of a single device type, in order to import it to another system.
I eventually found the solution:
That wasn't at all obvious at first.
I have two other ideas which might help:
I can raise those as separate FRs if you like.
The text was updated successfully, but these errors were encountered: