starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Adding the required fields in netbox.netbox.netbox_rack module #11356

New Issue
Closed
opened 2025-12-29 21:44:08 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:44:08 +01:00
Owner
Copy Link

Originally created by @Kowthem2910 on GitHub (Jul 8, 2025).

NetBox version

4.1

Feature type

Data model extension

Proposed functionality

It is required because the fields in this module needs to matched with the fields avilable in netbix on order to create the rack with the required fields.

Required fields:

  • rack_type
  • airflow

Use case

Depends the rack in different regions their type and airflow is mandatory to be assigned in organization point of view

Database changes

No response

External dependencies

No response

Originally created by @Kowthem2910 on GitHub (Jul 8, 2025). ### NetBox version 4.1 ### Feature type Data model extension ### Proposed functionality It is required because the fields in this module needs to matched with the fields avilable in netbix on order to create the rack with the required fields. Required fields: - rack_type - airflow ### Use case Depends the rack in different regions their type and airflow is mandatory to be assigned in organization point of view ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:44:08 +01:00
adam closed this issue 2025-12-29 21:44:08 +01:00
adam commented 2025-12-29 21:44:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 9, 2025):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Jul 9, 2025): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:44:09 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 17, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Jul 17, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:44:09 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 24, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Jul 24, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure status: revisions needed type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11356
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?