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

Accessing Fully Rendered Config Context Data is not Clear When Using Export Templates #4701

New Issue
Closed
opened 2025-12-29 19:19:37 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:19:37 +01:00
Owner
Copy Link

Originally created by @tcaiazza on GitHub (Mar 25, 2021).

Originally assigned to: @tcaiazza on GitHub.

Change Type

Addition

Area

  • Installation instructions
  • Configuration parameters
  • Functionality/features
  • REST API
  • Administration/development
  • Other

Proposed Changes

The combination of export templates and config context data are extremely powerful, but use the two in combination isn't as intuitive as accessing ofter attributes within an object. In order to access the fully rendered config context for an object, you need to use the function get_config_context() in the jinja template, which does not appear to be documented anywhere.

Originally created by @tcaiazza on GitHub (Mar 25, 2021). Originally assigned to: @tcaiazza on GitHub. ### Change Type Addition ### Area - [ ] Installation instructions - [ ] Configuration parameters - [ ] Functionality/features - [ ] REST API - [ ] Administration/development - [ ] Other ### Proposed Changes The combination of export templates and config context data are extremely powerful, but use the two in combination isn't as intuitive as accessing ofter attributes within an object. In order to access the fully rendered config context for an object, you need to use the function `get_config_context()` in the jinja template, which does not appear to be documented anywhere.
adam added the status: acceptedtype: documentation labels 2025-12-29 19:19:37 +01:00
adam closed this issue 2025-12-29 19:19:37 +01:00
adam commented 2025-12-29 19:19:38 +01:00
Author
Owner
Copy Link

@tcaiazza commented on GitHub (Apr 5, 2021):

I'd be happy to write the documentation myself, I just need the issue be accepted.

@tcaiazza commented on GitHub (Apr 5, 2021): I'd be happy to write the documentation myself, I just need the issue be accepted.
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: accepted type: documentation
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#4701
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?