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

Possibility to order scripts #5434

New Issue
Closed
opened 2025-12-29 19:27:54 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:27:54 +01:00
Owner
Copy Link

Originally created by @maximumG on GitHub (Sep 28, 2021).

Originally assigned to: @maximumG on GitHub.

NetBox version

v2.11.12

Feature type

Change to existing functionality

Proposed functionality

As of Netbox 2.11.x, scripts are automatically discovered and rendered in the UI (extras/scripts/). The order of the scripts is based on alphabetical order.

We propose the possibility for the developer to order the scripts listing inside a python module. We'd like to propose the same implementation as was done for reports in PR #7369.


MySuperScript(Script)
    pass

MySecondSuperScript(Script)
    pass

script_order = (MySuperScript, MySecondSuperScript)

Use case

Adding the possibility to order scripts would allow to present some kind of script's workflow within a specific module easily.

Database changes

No response

External dependencies

No response

Originally created by @maximumG on GitHub (Sep 28, 2021). Originally assigned to: @maximumG on GitHub. ### NetBox version v2.11.12 ### Feature type Change to existing functionality ### Proposed functionality As of Netbox 2.11.x, scripts are automatically discovered and rendered in the UI (extras/scripts/). The order of the scripts is based on alphabetical order. We propose the possibility for the developer to order the scripts listing inside a python module. We'd like to propose the same implementation as was done for reports in PR #7369. ```python MySuperScript(Script) pass MySecondSuperScript(Script) pass script_order = (MySuperScript, MySecondSuperScript) ``` ### Use case Adding the possibility to order scripts would allow to present some kind of script's workflow within a specific module easily. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:27:55 +01:00
adam closed this issue 2025-12-29 19:27:55 +01:00
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: 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#5434
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?