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

Introduce a custom permission action for rendering configuration templates #9880

New Issue
Closed
opened 2025-12-29 21:23:56 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:23:56 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jun 21, 2024).

Originally assigned to: @jnovinger on GitHub.

NetBox version

v4.0.5

Feature type

Change to existing functionality

Proposed functionality

Rendering a configuration template for a device or virtual machine will require a new custom permission action, render_config.

Currently, rendering a configuration template via the UI does not require any permissions beyond view for the relevant object type (e.g. dcim.view_device). However, rendering a configuration template via the REST API currently requires the add permission (e.g. dcim.add_device). While the requirement for write permission makes sense for API calls (because we're accepting and processing arbitrary user data), the specific permission for creating devices does not and has been captured as a bug in #14634.

Use case

This new permission action can be used to allow config rendering via the REST API without needing to grant users permission to create new devices/VMs.

Database changes

None

External dependencies

None

Originally created by @jeremystretch on GitHub (Jun 21, 2024). Originally assigned to: @jnovinger on GitHub. ### NetBox version v4.0.5 ### Feature type Change to existing functionality ### Proposed functionality Rendering a configuration template for a device or virtual machine will require a new custom permission action, `render_config`. Currently, rendering a configuration template via the UI does not require any permissions beyond `view` for the relevant object type (e.g. `dcim.view_device`). However, rendering a configuration template via the REST API currently requires the `add` permission (e.g. `dcim.add_device`). While the requirement for write permission makes sense for API calls (because we're accepting and processing arbitrary user data), the specific permission for creating devices does not and has been captured as a bug in #14634. ### Use case This new permission action can be used to allow config rendering via the REST API without needing to grant users permission to create new devices/VMs. ### Database changes None ### External dependencies None
adam closed this issue 2025-12-29 21:23:57 +01:00
adam commented 2025-12-29 21:23:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 21, 2024):

Tagging #14400 as related

@jeremystretch commented on GitHub (Jun 21, 2024): Tagging #14400 as related
adam commented 2025-12-29 21:23:58 +01:00
Author
Owner
Copy Link

@mraerino commented on GitHub (Sep 9, 2024):

could we do the same for the /api/extras/config-templates/{id}/render/ route? it seems logical since both of them basically have the same implications and similar use cases. only difference is that this API route does not require any permissions on a device, just on the template itself

@mraerino commented on GitHub (Sep 9, 2024): could we do the same for the `/api/extras/config-templates/{id}/render/` route? it seems logical since both of them basically have the same implications and similar use cases. only difference is that this API route does not require any permissions on a device, just on the template itself
adam commented 2025-12-29 21:23:58 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 25, 2025):

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 (Apr 25, 2025): 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/main/CONTRIBUTING.md).
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 breaking change complexity: medium netbox status: accepted topic: templating 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#9880
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?