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

Custom fields with option to be hidden (treat like secret) #8333

New Issue
Closed
opened 2025-12-29 20:35:27 +01:00 by adam · 6 comments
adam commented 2025-12-29 20:35:27 +01:00
Owner
Copy Link

Originally created by @mtnetronik on GitHub (Jul 13, 2023).

NetBox version

v3.5.5

Feature type

Change to existing functionality

Proposed functionality

This request is related to #11623.
Is it possible to add option in custom field that this field will be hidden, like field from Wireless -> Wireless LAN -> PSK ?

In the other words:
In Wireless -> Wireless LANs you added additional field "Pre-shared key" and it store in DB in wireless_wirelesslan table in auth_psk. When you try to view this value on right of this field you have button show/hide secret. When you try to edit this field you see dots instead real value.
So it is possible to add this option (button with show/hide secret and dots when editing) to use in Custom Fields?

Use case

For example for Mikrotik wireless devices where we are using few wireless protocols like 802.11 and nv2 and passwords are different.

Database changes

Yes, I think - new column in extras_customfield table what will store information if custom field will be treated like secret or not.

External dependencies

No response

Originally created by @mtnetronik on GitHub (Jul 13, 2023). ### NetBox version v3.5.5 ### Feature type Change to existing functionality ### Proposed functionality This request is related to #11623. Is it possible to add option in custom field that this field will be hidden, like field from Wireless -> Wireless LAN -> PSK ? In the other words: In Wireless -> Wireless LANs you added additional field "Pre-shared key" and it store in DB in wireless_wirelesslan table in auth_psk. When you try to view this value on right of this field you have button show/hide secret. When you try to edit this field you see dots instead real value. So it is possible to add this option (button with show/hide secret and dots when editing) to use in Custom Fields? ### Use case For example for Mikrotik wireless devices where we are using few wireless protocols like 802.11 and nv2 and passwords are different. ### Database changes Yes, I think - new column in extras_customfield table what will store information if custom field will be treated like secret or not. ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:35:27 +01:00
adam closed this issue 2025-12-29 20:35:27 +01:00
adam commented 2025-12-29 20:35:27 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jul 13, 2023):

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.

@abhi1693 commented on GitHub (Jul 13, 2023): 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 20:35:28 +01:00
Author
Owner
Copy Link

@mtnetronik commented on GitHub (Jul 14, 2023):

@abhi1693 Thank you for response. I am user not programmer, so it would be nice if you helped me describe it correctly.
In my words:
In this topic #11623
In Wireless -> Wireless LANs you added additional field "Pre-shared key" and it store in DB in wireless_wirelesslan table in auth_psk. When you try to view this value on right of this field you have button show/hide secret. When you try to edit this field you see dots instead real value.
So it is possible to add this option (button with show/hide secret and dots when editing) to use in Custom Fields?

@mtnetronik commented on GitHub (Jul 14, 2023): @abhi1693 Thank you for response. I am user not programmer, so it would be nice if you helped me describe it correctly. In my words: In this topic #11623 In Wireless -> Wireless LANs you added additional field "Pre-shared key" and it store in DB in wireless_wirelesslan table in auth_psk. When you try to view this value on right of this field you have button show/hide secret. When you try to edit this field you see dots instead real value. So it is possible to add this option (button with show/hide secret and dots when editing) to use in Custom Fields?
adam commented 2025-12-29 20:35:28 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jul 14, 2023):

Please update this in your description in your original post so that other maintainers can also look into this.

@abhi1693 commented on GitHub (Jul 14, 2023): Please update this in your description in your original post so that other maintainers can also look into this.
adam commented 2025-12-29 20:35:28 +01:00
Author
Owner
Copy Link

@mtnetronik commented on GitHub (Jul 18, 2023):

@abhi1693 I updated a title and description.

@mtnetronik commented on GitHub (Jul 18, 2023): @abhi1693 I updated a title and description.
adam commented 2025-12-29 20:35:28 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 16, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jan 16, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:35:28 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 15, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Feb 15, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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: under review 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#8333
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?