Support secrets fields in virtual machines #4278

Closed
opened 2025-12-29 18:34:23 +01:00 by adam · 1 comment
Owner

Originally created by @apc-mizouchi on GitHub (Nov 16, 2020).

Environment

  • Python version: 3.6
  • NetBox version: 2.9.9

Proposed Functionality

Support secrets fields in virtual machines.

Use Case

A secrete fields in virtual machines can be stored virtual machin's credentials.
Now virtual machin's credentials may be stored in custom fields. But virtual machin's credentials is revealed by anyone..

Database Changes

I don't believe there would be a requirement for any database changes.

External Dependencies

None.

Originally created by @apc-mizouchi on GitHub (Nov 16, 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/g/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 * NetBox version: 2.9.9 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Support secrets fields in virtual machines. <!-- 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 A secrete fields in virtual machines can be stored virtual machin's credentials. Now virtual machin's credentials may be stored in custom fields. But virtual machin's credentials is revealed by anyone.. <!-- 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 don't believe there would be a requirement for any database changes. <!-- 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.
adam added the status: duplicate label 2025-12-29 18:34:23 +01:00
adam closed this issue 2025-12-29 18:34:23 +01:00
Author
Owner

@jeremystretch commented on GitHub (Nov 16, 2020):

Duplicate of #1503

@jeremystretch commented on GitHub (Nov 16, 2020): Duplicate of #1503
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4278