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

Assign secrets to virtual machines #1229

New Issue
Closed
opened 2025-12-29 16:30:24 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:30:24 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Sep 15, 2017).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: v2.2-beta1

Description

Currently you can attach secrets to Devices but not Virtual Machines.

Use cases:

  • Storing per-VM administrator/console logins
  • Someone who uses secrets for Devices will probably want to use them for VMs too.
  • Conversely, someone who finds they cannot use secrets for VMs (and hence needs an external solution) will likely use the external solution for Devices too.

Aside: I don't use netbox secrets myself for various reasons. I am entering this ticket so that a decision can be recorded either way.

It might be worth a poll to see who does use this feature; and if it's not widely used, consider removing it.

Originally created by @candlerb on GitHub (Sep 15, 2017). ### Issue type [X] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: v2.2-beta1 ### Description Currently you can attach secrets to Devices but not Virtual Machines. Use cases: * Storing per-VM administrator/console logins * Someone who uses secrets for Devices will probably want to use them for VMs too. * Conversely, someone who finds they cannot use secrets for VMs (and hence needs an external solution) will likely use the external solution for Devices too. --- Aside: I don't use netbox secrets myself for various reasons. I am entering this ticket so that a decision can be recorded either way. It might be worth a poll to see who *does* use this feature; and if it's not widely used, consider removing it.
adam closed this issue 2025-12-29 16:30:24 +01:00
adam commented 2025-12-29 16:30:24 +01:00
Author
Owner
Copy Link

@darkstar commented on GitHub (Sep 18, 2017):

It was made quite clear that NetBox is not intended for that. See https://github.com/digitalocean/netbox/issues/142#issuecomment-256086213 for a comment on secrets for VMs.

I would probably use that feature if it were available, but I don't particularly need it (I have other means to store the secrets for VMs, and I kind of agree with the fact that NetBox is not designed to reach that far into the administrative level of the VMs)

@darkstar commented on GitHub (Sep 18, 2017): It was made quite clear that NetBox is not intended for that. See https://github.com/digitalocean/netbox/issues/142#issuecomment-256086213 for a comment on secrets for VMs. I would probably use that feature if it were available, but I don't particularly need it (I have other means to store the secrets for VMs, and I kind of agree with the fact that NetBox is not designed to reach that far into the administrative level of the VMs)
adam commented 2025-12-29 16:30:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 18, 2017):

@darkstar That comment was made before the v2.2 beta introduced support for virtual machines and clusters. v2.2 will definitely have virtual machines; whether or not we want to extend secrets to them and other objects (see #1503) is still open for discussion.

@jeremystretch commented on GitHub (Sep 18, 2017): @darkstar That comment was made before the v2.2 beta introduced support for virtual machines and clusters. v2.2 will definitely have virtual machines; whether or not we want to extend secrets to them and other objects (see #1503) is still open for discussion.
adam commented 2025-12-29 16:30:24 +01:00
Author
Owner
Copy Link

@darkstar commented on GitHub (Sep 19, 2017):

@jeremystretch I am aware of that but you later posted that you're still leaning towards "no" on the issue, and for the same reasons (see https://github.com/digitalocean/netbox/issues/142#issuecomment-326590192). Maybe I should have linked to that comment instead ;-)

The idea of #1503 never crossed my mind... it seems there are quite a few cases where secrets could be useful. If so, it certainly makes sense to also add them to VMs/Clusters

@darkstar commented on GitHub (Sep 19, 2017): @jeremystretch I am aware of that but you later posted that you're still leaning towards "no" on the issue, and for the same reasons (see https://github.com/digitalocean/netbox/issues/142#issuecomment-326590192). Maybe I should have linked to that comment instead ;-) The idea of #1503 never crossed my mind... it seems there are quite a few cases where secrets could be useful. If so, it certainly makes sense to also add them to VMs/Clusters
adam commented 2025-12-29 16:30:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 20, 2017):

I'm going to close this issue for now in favor of #1503, which would cover extending secrets to VMs. If #1503 falls through, this issue can be re-opened.

@jeremystretch commented on GitHub (Sep 20, 2017): I'm going to close this issue for now in favor of #1503, which would cover extending secrets to VMs. If #1503 falls through, this issue can be re-opened.
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#1229
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?