Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce signals indicating the execution or termination of a job #14365

Closed
jeremystretch opened this issue Nov 28, 2023 · 0 comments
Closed

Introduce signals indicating the execution or termination of a job #14365

jeremystretch opened this issue Nov 28, 2023 · 0 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone
v3.7

Comments

@jeremystretch
Copy link
Member

NetBox version

v3.6.5

Feature type

New functionality

Proposed functionality

Introduce two new signals, job_start and job_end, which fire when a job is executed or terminated, respectively. This will allow us to move the trigger_webhooks() method from the Job model into a standalone receiver.

Use case

Exposing these signals standardizes event behavior in #14132 and enables plugins to interact with job events.

Database changes

N/A

External dependencies

N/A
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Nov 28, 2023
@jeremystretch jeremystretch added this to the v3.7 milestone Nov 28, 2023
@jeremystretch jeremystretch self-assigned this Nov 29, 2023
@jeremystretch jeremystretch mentioned this issue Nov 30, 2023
Merged
jeremystretch added a commit that referenced this issue Dec 1, 2023
@jeremystretch
Closes #14365: Introduce job_start and job_end signals (#14393)
4fc0a99 
* Introduce job_start and job_end signals, and receivers to process event rules

* Complete signals documentation
@jeremystretch jeremystretch mentioned this issue Dec 29, 2023
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
v3.7
Development

No branches or pull requests
1 participant
@jeremystretch