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

Expand permissions to include "Rendered Config" contexts. #11897

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

Originally created by @bctiemann on GitHub (Dec 5, 2025).

Originally assigned to: @jnovinger on GitHub.

NetBox version

v4.4.7

Feature type

Data model extension

Proposed functionality

Feature request. In short, our customer would like to be able to limit whether a user of NetBox can view "Rendered Config" and other config contexts from within the "Devices" model in NetBox.

Use case

This is to ensure that when configs are rendered along with their passwords and other secrets, these are not openly visible to users whom they don't want to be able to view this information.

You can sort do this to a limited degree by denying access to Extras>Contexts, however the "Rendered Config" is visible regardless of this still on the device itself.

Could we expand permissions to include this?

Database changes

No response

External dependencies

No response

Originally created by @bctiemann on GitHub (Dec 5, 2025). Originally assigned to: @jnovinger on GitHub. ### NetBox version v4.4.7 ### Feature type Data model extension ### Proposed functionality Feature request. In short, our customer would like to be able to limit whether a user of NetBox can view "Rendered Config" and other config contexts from within the "Devices" model in NetBox. ### Use case This is to ensure that when configs are rendered along with their passwords and other secrets, these are not openly visible to users whom they don't want to be able to view this information. You can sort do this to a limited degree by denying access to Extras>Contexts, however the "Rendered Config" is visible regardless of this still on the device itself. Could we expand permissions to include this? ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: mediumnetbox labels 2025-12-29 21:51:18 +01:00
adam closed this issue 2025-12-29 21:51:19 +01:00
adam commented 2025-12-29 21:51:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 5, 2025):

Is this addressed by FR #16681 in the upcoming v4.5 release?

@jeremystretch commented on GitHub (Dec 5, 2025): Is this addressed by FR #16681 in the upcoming v4.5 release?
adam commented 2025-12-29 21:51:19 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Dec 12, 2025):

Is this addressed by FR #16681 in the upcoming v4.5 release?

Almost, the added render_config permission added in #16681 provides the machinery, but the UI view is not using it. PR shortly.

@jnovinger commented on GitHub (Dec 12, 2025): > Is this addressed by FR [#16681](https://github.com/netbox-community/netbox/issues/16681) in the upcoming v4.5 release? Almost, the added `render_config` permission added in #16681 provides the machinery, but the UI view is not using it. PR shortly.
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 complexity: medium netbox status: accepted 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#11897
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?