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 UI Link #10018

New Issue
Closed
opened 2025-12-29 21:25:48 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:25:48 +01:00
Owner
Copy Link

Originally created by @mcrute on GitHub (Jul 28, 2024).

NetBox version

v4.0.3

Feature type

New functionality

Proposed functionality

For the UI rendering of custom fields could you add the ability to render the value as a link using a placeholder of some form that opens in a new tab?

Something like:

UI Link Template: https://somehost.example.com/passwords/{value}

If this field was blank then the current rendering logic would apply.

Use case

We use Netbox as the source of truth for infrastructure data but occasionally there is secret data (keys, root passwords, etc...) that are stored in an external system designed for secure secret storage. We're currently using a custom field to attach a sub-path to those secrets in the Netbox record but would like to make it easy for our techs to click through directly to the secret itself.

For example, today we would store something like this:

Root Credential: passwords/site1/hostname-root

And a tech now has to copy this out of Netbox and paste it into the secret management system to search for those secrets. Ideally we'd have the UI rendering deep-link directly into the secret management system so they can click straight through to it. We would like this to open in a new tab so that techs don't lose their place in Netbox when they go to lookup a secret.

Database changes

No response

External dependencies

No response

Originally created by @mcrute on GitHub (Jul 28, 2024). ### NetBox version v4.0.3 ### Feature type New functionality ### Proposed functionality For the UI rendering of custom fields could you add the ability to render the value as a link using a placeholder of some form that opens in a new tab? Something like: ``` UI Link Template: https://somehost.example.com/passwords/{value} ``` If this field was blank then the current rendering logic would apply. ### Use case We use Netbox as the source of truth for infrastructure data but occasionally there is secret data (keys, root passwords, etc...) that are stored in an external system designed for secure secret storage. We're currently using a custom field to attach a sub-path to those secrets in the Netbox record but would like to make it easy for our techs to click through directly to the secret itself. For example, today we would store something like this: ``` Root Credential: passwords/site1/hostname-root ``` And a tech now has to copy this out of Netbox and paste it into the secret management system to search for those secrets. Ideally we'd have the UI rendering deep-link directly into the secret management system so they can click straight through to it. We would like this to open in a new tab so that techs don't lose their place in Netbox when they go to lookup a secret. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: under review labels 2025-12-29 21:25:48 +01:00
adam closed this issue 2025-12-29 21:25:48 +01:00
adam commented 2025-12-29 21:25:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2024):

It sounds like you're describing the functionality provided by custom links, which can (using a Jinja2 template) reference the value of a custom field on an object.

@jeremystretch commented on GitHub (Jul 29, 2024): It sounds like you're describing the functionality provided by [custom links](https://netboxlabs.com/docs/netbox/en/stable/customization/custom-links/), which can (using a Jinja2 template) reference the value of a custom field on an object.
adam commented 2025-12-29 21:25:49 +01:00
Author
Owner
Copy Link

@mcrute commented on GitHub (Jul 29, 2024):

Oh yeah, this is exactly perfect! Sorry for the noise and missing something so obvious!

@mcrute commented on GitHub (Jul 29, 2024): Oh yeah, this is exactly perfect! Sorry for the noise and missing something so obvious!
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 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#10018
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?