Limit Custom Scripts to manual/event execution #191

New Issue

MrUnknownDE · 2026-04-05T16:22:50+02:00

MrUnknownDE commented

2026-04-05 16:22:50 +02:00

Originally created by @mburggraf on 3/8/2026

NetBox version

v4.5.4

Feature type

Change to existing functionality

Proposed functionality

It should be possible, to define if a custom script is allowed to be executed by event rule or manually.

For example you could define some new script attributes (similar to scheduling_enabled), like event_enabled and manual_enabled.
If event_enabled is set to false, the corresponding script won't appear in the drop-down menu when creating an event rule. If manual_enabled is false, there won't be any run-button in the script view.

Another way to achieve the same behavior could be, by defining different run() methods for manual and event execution, though this would break downward compatibility.

Use case

Currently every custom script can be executed manually with the "run" button, as well as being set for an event rule.

However some scripts may be specifically written to be called in case of an event, while others may require manual settings and can't be meaningfully be executed by event handler.

Database changes

Don't know, probably not.

External dependencies

No response

*Originally created by @mburggraf on 3/8/2026* ### NetBox version v4.5.4 ### Feature type Change to existing functionality ### Proposed functionality It should be possible, to define if a custom script is allowed to be executed by event rule or manually. For example you could define some new script attributes (similar to `scheduling_enabled`), like `event_enabled` and `manual_enabled`. If `event_enabled` is set to `false`, the corresponding script won't appear in the drop-down menu when creating an event rule. If `manual_enabled` is `false`, there won't be any run-button in the script view. Another way to achieve the same behavior could be, by defining different `run()` methods for manual and event execution, though this would break downward compatibility. ### Use case Currently every custom script can be executed manually with the "run" button, as well as being set for an event rule. However some scripts may be specifically written to be called in case of an event, while others may require manual settings and can't be meaningfully be executed by event handler. ### Database changes Don't know, probably not. ### External dependencies _No response_

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

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

No Label netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: under review status: under review status: under review status: under review topic: custom scripts topic: custom scripts topic: custom scripts topic: custom scripts type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#191