Skip to content

Automate export of DeviceTypes in YAML export #3801

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.

Sign up for GitHub

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

Jump to bottom
Closed
jeremystretch opened this issue Dec 27, 2019 · 0 comments
Closed

Automate export of DeviceTypes in YAML export #3801

jeremystretch opened this issue Dec 27, 2019 · 0 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@jeremystretch
Copy link
Member

Environment

  • Python version: 3.6.8
  • NetBox version: 2.7-beta1

Proposed Functionality

Change the built-in DeviceType export format from CSV to YAML, with each DeviceType instance represented as a discrete YAML document

Use Case

Now that YAML-based import is supported, it makes sense to export DeviceTypes as YAML rather than CSV. This should also help people more easily contribute to the community device type library.

Database Changes

None

External Dependencies

None
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Dec 27, 2019
@jeremystretch jeremystretch self-assigned this Jan 9, 2020
@jeremystretch jeremystretch mentioned this issue Jan 13, 2020
Merged
jeremystretch added a commit that referenced this issue Jan 13, 2020
@jeremystretch
Changelog for #3801
ce0e351
jeremystretch added a commit that referenced this issue Jan 13, 2020
@jeremystretch
Merge pull request #3911 from netbox-community/3801-devicetype-yaml
8f636d9 
Closes #3801: Change DeviceType export from CSV to YAML
@jeremystretch jeremystretch mentioned this issue Jan 16, 2020
Merged
@u1735067 u1735067 mentioned this issue Feb 26, 2020
Closed
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremystretch