Add a delete lock feature. #3593

New Issue

adam · 2025-12-29T18:30:02+01:00

adam commented

2025-12-29 18:30:02 +01:00

Originally created by @kevinreniers on GitHub (Apr 21, 2020).

Environment

Python version: 3.6.8
NetBox version: 2.7.12

Proposed Functionality

In order to prevent accidental deletion we would like to be able to "lock" resources against deletion and/or updating.

Use Case

Preventing mistakes when a given resource really shouldn't be deleted or updated in any case. I think this is still useful in all cases even when the users are careful. It's all just a matter of time before someone accidentally removes something they shouldn't have removed.

For us, we'll be granting limited write access to other teams or members outside of our team in order to enable orchestration. We want to allow them to delete and update their own prefixes at will, but there are a few that are key to orchestration that they shouldn't have to touch. As such, a lock mechanism could make this easier for us.

Database Changes

A potential implementation could add a lock_type enum to each supported database table indicating the kind of lock we're talking about. Azure, for instance, uses a "CannotDelete" and "ReadOnly" lock.

External Dependencies

None, I think?

Originally created by @kevinreniers on GitHub (Apr 21, 2020). ### Environment * Python version: 3.6.8 * NetBox version: 2.7.12 ### Proposed Functionality In order to prevent accidental deletion we would like to be able to "lock" resources against deletion and/or updating. ### Use Case Preventing mistakes when a given resource *really* shouldn't be deleted or updated in any case. I think this is still useful in all cases even when the users are careful. It's all just a matter of time before someone accidentally removes something they shouldn't have removed. For us, we'll be granting limited write access to other teams or members outside of our team in order to enable orchestration. We want to allow them to delete and update their own prefixes at will, but there are a few that are key to orchestration that they shouldn't have to touch. As such, a lock mechanism could make this easier for us. ### Database Changes A potential implementation could add a lock_type enum to each supported database table indicating the kind of lock we're talking about. Azure, for instance, uses a "CannotDelete" and "ReadOnly" lock. ### External Dependencies None, I think?

adam closed this issue

2025-12-29 18:30:02 +01:00

adam commented

2025-12-29 18:30:03 +01:00

@jeremystretch commented on GitHub (Apr 21, 2020):

I doubt we'd implement an arbitrary "deletion lock," but your use case is likely covered by the implementation of role-based access control (#554).

@jeremystretch commented on GitHub (Apr 21, 2020): I doubt we'd implement an arbitrary "deletion lock," but your use case is likely covered by the implementation of role-based access control (#554).

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#3593