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

Add branching provider to configuration #10531

New Issue
Closed
opened 2025-12-29 21:32:46 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:32:46 +01:00
Owner
Copy Link

Originally created by @arthanson on GitHub (Dec 2, 2024).

Originally assigned to: @arthanson on GitHub.

NetBox version

v4.1.7

Feature type

New functionality

Triage priority

N/A

Proposed functionality

Add branching provider support as a configuration parameter and modify the script running code to take into account branching support.

Use case

This will allow scripts with script parameters to be run while in the context of a branch. This requires changes to the core of NetBox in the script running code as well as the branching plugin to support this.

Database changes

N/A

External dependencies

N/A

Originally created by @arthanson on GitHub (Dec 2, 2024). Originally assigned to: @arthanson on GitHub. ### NetBox version v4.1.7 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality Add branching provider support as a configuration parameter and modify the script running code to take into account branching support. ### Use case This will allow scripts with script parameters to be run while in the context of a branch. This requires changes to the core of NetBox in the script running code as well as the branching plugin to support this. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: medium labels 2025-12-29 21:32:46 +01:00
adam closed this issue 2025-12-29 21:32:46 +01:00
adam commented 2025-12-29 21:32:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 12, 2024):

Going to close this out in favor of the similar but more generic approach proposed in FR #18211 (which largely builds on the work in @arthanson's PR #18137).

@jeremystretch commented on GitHub (Dec 12, 2024): Going to close this out in favor of the similar but more generic approach proposed in FR #18211 (which largely builds on the work in @arthanson's PR #18137).
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 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#10531
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?