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

Azure Options #3576

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

Originally created by @colin-small on GitHub (Apr 15, 2020).

Environment

  • Python version: 3.6
  • NetBox version: 2.7.6

Proposed Functionality

I would like to see options throughout Netbox that are more Azure/cloud friendly for documenting Azure based "devices" and virtual networks.

For Azure specific stuff like maybe a way to assign resource groups or is it a dynamic or static public IP.. vnets... IaaS options.. subscriptions networks live in.. ExpressRoute circuit type and data for private peering/public peering etc.. vnet peering to tie vnets together.. route tables/routes. product SKU's to document the type of object because it may have limitations based on the SKU.

This is a broad topic and I am just doing a brain dump of some useful things that come to mind. If anyone else uses Azure and Netbox maybe they can chime in and add more options that would add value.

If this doesn't paint the picture so to speak, I can start documenting as I add things to Netbox where it would have been nice to have X option each time and start adding them here.

Really I am just saying from a high level that Azure specific options would help me out a lot as I'm living in an onprem/cloud world when it comes to infrastructure/networking.

Use Case

See above

Database Changes

I'm not sure.

External Dependencies

None I am aware of.

Originally created by @colin-small on GitHub (Apr 15, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 <!-- Example: 3.6.9 --> * NetBox version: 2.7.6 <!-- Example: 2.7.3 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality I would like to see options throughout Netbox that are more Azure/cloud friendly for documenting Azure based "devices" and virtual networks. For Azure specific stuff like maybe a way to assign resource groups or is it a dynamic or static public IP.. vnets... IaaS options.. subscriptions networks live in.. ExpressRoute circuit type and data for private peering/public peering etc.. vnet peering to tie vnets together.. route tables/routes. product SKU's to document the type of object because it may have limitations based on the SKU. This is a broad topic and I am just doing a brain dump of some useful things that come to mind. If anyone else uses Azure and Netbox maybe they can chime in and add more options that would add value. If this doesn't paint the picture so to speak, I can start documenting as I add things to Netbox where it would have been nice to have X option each time and start adding them here. Really I am just saying from a high level that Azure specific options would help me out a lot as I'm living in an onprem/cloud world when it comes to infrastructure/networking. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case See above <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes I'm not sure. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None I am aware of.
adam closed this issue 2025-12-29 18:29:58 +01:00
adam commented 2025-12-29 18:29:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 15, 2020):

Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using one of the templates provided here. For general discussion, questions, or assistance with installation issues, please post to our mailing list instead.

@jeremystretch commented on GitHub (Apr 15, 2020): Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using one of the templates provided [here](https://github.com/netbox-community/netbox/issues/new/choose). For general discussion, questions, or assistance with installation issues, please post to our [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss) instead.
adam commented 2025-12-29 18:29:58 +01:00
Author
Owner
Copy Link

@colin-small commented on GitHub (Apr 15, 2020):

Did you close this issue because I didn't provide a list of specific items but rather a broader scope? Just trying to understand. Thanks.

@colin-small commented on GitHub (Apr 15, 2020): Did you close this issue because I didn't provide a list of specific items but rather a broader scope? Just trying to understand. Thanks.
adam commented 2025-12-29 18:29:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 15, 2020):

Yes; issues are intended for directly actionable work, not general discussion. The mailing list is much better suited to open-ended discussion. Once you've identified specific features you'd like to propose, you're welcome to open individual issues for them.

@jeremystretch commented on GitHub (Apr 15, 2020): Yes; issues are intended for directly actionable work, not general discussion. The mailing list is much better suited to open-ended discussion. Once you've identified specific features you'd like to propose, you're welcome to open individual issues for them.
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#3576
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?