-
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
Add JSON/YAML import support for all objects #4347
Comments
This is really cool, thanks! Are there any plans to allow import of a full export with multiple items (for examples device types) at once? This would be really awesome! Thanks and best |
One use case for this feature: The changelog holds the JSON object for deleted objects, and it would be very convenient if this could be fed directly into an Import Device dialog to get an undo feature. (Since the JSON contains numeric ids for stuff like |
Punting this to v3.2 as we'll likely need to refactor the current JSON/YAML import view substantially to accommodate models beyond device type. |
The import/export of device types already supports YAML but has limitations (discussion #6228). It works differently from normal import/export so don't know if would fall under the umbrella of this issue. The ability to automatically create the linked objects is nice but the inability to bulk import isn't. If there is to be a refactor consideration of device types would be useful. |
Also looking for this type of thing. In this release, would it be possible to do that via the API too? |
What do you mean by "do that via the API too" ? |
Bulk import NetBox information in json format via the API as well as in the GUI. In this issue, my understanding is that you could bulk import yaml AND json, therefore I am assuming it's just the GUI. |
Proposed Changes
Allow users to import objects in YAML or JSON format in addition to the existing support for CSV. YAML/JSON support was introduced for device types in #451; this extends that same functionality to all models.
Justification
JSON and YAML offer greater flexibility than CSV in incorporating related instances, as well as referencing parent objects.
The text was updated successfully, but these errors were encountered: