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

Access to Config Context from Custom Link #6997

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

Originally created by @tomasherout on GitHub (Sep 19, 2022).

NetBox version

v.3.3.4

Feature type

New functionality

Proposed functionality

Custom Link has access to Custom Fields via {{ object.cf.foo }} but seems it can't access to Config Context of particular device.

Use case

Provide link to other systems where related data are stored in Config Context.

Database changes

No response

External dependencies

No response

Originally created by @tomasherout on GitHub (Sep 19, 2022). ### NetBox version v.3.3.4 ### Feature type New functionality ### Proposed functionality _Custom Link_ has access to _Custom Fields_ via `{{ object.cf.foo }}` but seems it can't access to _Config Context_ of particular device. ### Use case Provide link to other systems where related data are stored in Config Context. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:47:36 +01:00
adam closed this issue 2025-12-29 19:47:36 +01:00
adam commented 2025-12-29 19:47:37 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Sep 19, 2022):

It works for me when testing:

{{object.get_config_context().name_of_key}}

@kkthxbye-code commented on GitHub (Sep 19, 2022): It works for me when testing: `{{object.get_config_context().name_of_key}}`
adam commented 2025-12-29 19:47:37 +01:00
Author
Owner
Copy Link

@tomasherout commented on GitHub (Sep 19, 2022):

Cool, works. Many thanks 👍

It would be good to mention it at https://docs.netbox.dev/en/stable/customization/custom-links/

@tomasherout commented on GitHub (Sep 19, 2022): Cool, works. Many thanks 👍 It would be good to mention it at https://docs.netbox.dev/en/stable/customization/custom-links/
adam commented 2025-12-29 19:47:38 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Sep 19, 2022):

I think it's a hard balance, as we already mention the following:

Checking the REST API representation of an object is generally a convenient way to determine what attributes are available. You can also reference the NetBox source code directly for a comprehensive list.

Custom scripts, reports, custom URL's etc. are really all power user features and it's impossible to document everything that is possible with the internal netbox objects. If you feel like config contexts deserves a concrete mention in the docs you are welcome to create a documentation issue instead.

@kkthxbye-code commented on GitHub (Sep 19, 2022): I think it's a hard balance, as we already mention the following: >Checking the REST API representation of an object is generally a convenient way to determine what attributes are available. _**You can also reference the NetBox source code directly for a comprehensive list.**_ Custom scripts, reports, custom URL's etc. are really all power user features and it's impossible to document everything that is possible with the internal netbox objects. If you feel like config contexts deserves a concrete mention in the docs you are welcome to create a documentation issue instead.
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 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#6997
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?