-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add rack-types #3026
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
base: master
Are you sure you want to change the base?
Add rack-types #3026
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a new rack type definition for a Startech rack and updates the front image setting for an HPE device type, addressing issue #2618 and supporting the related Device-Type-Library-Import PR.
- Added a new YAML file for the Startech 4 Post 42U rack with key specifications.
- Updated the HPE OfficeConnect device type to set front_image to true.
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
rack-types/Startech/startech-4postrack42.yaml | Introduces a new rack type with specifications and includes commented alternatives for mounting depth and weight. |
device-types/HPE/OfficeConnect-1920-24G-PoE-180W.yml | Changes the front_image property from false to true. |
Comments suppressed due to low confidence (1)
device-types/HPE/OfficeConnect-1920-24G-PoE-180W.yml:8
- Verify that setting front_image to true is the intended change, and if so, ensure that associated tests and documentation reflect this update.
front_image: true
# Conflicts: # rack-types/Digitus/digitus-dn-19-07u-i-od.yml
This reverts commit bdd2760.
Hi @bastianleicht Thanks for the contribution, |
@harryajc The Pre-Commit Checks should already work? As far as I know, they are not limited to folders etc. Or am I wrong here? |
What Harry is mentioning is adding a new data type means we will need to build out the schemas and test cases. Also, the schema generation in NetBox proper will need to be updated to gather the variable details like we do with the device and module types |
@danner26 Right, I forgot that. I just added the Schema and Schema generation. It worked on my side. Do i need to add anything more? |
Okay, I think I now got everything. The Pytest is now working correctly and checking the files. |
As described in #2618
Implementation of the importer in: netbox-community/Device-Type-Library-Import#170