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

airflow direction #1071

New Issue
Closed
opened 2025-12-29 16:28:31 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:28:31 +01:00
Owner
Copy Link

Originally created by @devpets on GitHub (Jul 2, 2017).

Issue type: feature request

Python version:
NetBox version:

Would be nice to have an option to specify AIRFLOW direction of the device.

Originally created by @devpets on GitHub (Jul 2, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: feature request <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** **NetBox version:** <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> Would be nice to have an option to specify AIRFLOW direction of the device.
adam closed this issue 2025-12-29 16:28:31 +01:00
adam commented 2025-12-29 16:28:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 3, 2017):

This feature request lacks sufficient detail to be actionable. Per the contributing guidelines:

When submitting a feature request on GitHub, be sure to include the following:

  • A detailed description of the proposed functionality
  • A use case for the feature; who would use it and what value it would add to NetBox
  • A rough description of changes necessary to the database schema (if applicable)
  • Any third-party libraries or other resources which would be involved

Please extend the request so that it meets all of these requirements. If no response is received within a week, this issue will be closed.

@jeremystretch commented on GitHub (Jul 3, 2017): This feature request lacks sufficient detail to be actionable. Per the [contributing guidelines](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md): > When submitting a feature request on GitHub, be sure to include the following: > > * A detailed description of the proposed functionality > * A use case for the feature; who would use it and what value it would add to NetBox > * A rough description of changes necessary to the database schema (if applicable) > * Any third-party libraries or other resources which would be involved Please extend the request so that it meets all of these requirements. If no response is received within a week, this issue will be closed.
adam commented 2025-12-29 16:28:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 10, 2017):

Closing due to lack of activity.

@jeremystretch commented on GitHub (Jul 10, 2017): Closing due to lack of activity.
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
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#1071
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?