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

Rename JobResult to Job and move to the "core" app #7798

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

Originally created by @jeremystretch on GitHub (Mar 27, 2023).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

This proposal entails two changes:

  1. Name the JobResult class to Job
  2. Move the class from extras to the new core app

The REST API endpoint for jobs would thus move from /api/extras/job-results to /api/core/jobs/. Similarly, the JOBRESULT_RETENTION configuration parameter will be renamed to JOB_RETENTION.

Justification

The core app being introduced in v3.5 serves to hold models which are not directly useful but empower other functionality in NetBox. Jobs meet this criteria, similar to other models which are being introduced in core: DataSource, DataFile, and ManagedFile.

Renaming the class also feels appropriate as the model is used to track the entire lifecycle of a job, not just its result.

Originally created by @jeremystretch on GitHub (Mar 27, 2023). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes This proposal entails two changes: 1. Name the `JobResult` class to `Job` 2. Move the class from `extras` to the new `core` app The REST API endpoint for jobs would thus move from `/api/extras/job-results` to `/api/core/jobs/`. Similarly, the `JOBRESULT_RETENTION` configuration parameter will be renamed to `JOB_RETENTION`. ### Justification The `core` app being introduced in v3.5 serves to hold models which are not directly useful but empower other functionality in NetBox. Jobs meet this criteria, similar to other models which are being introduced in core: `DataSource`, `DataFile`, and `ManagedFile`. Renaming the class also feels appropriate as the model is used to track the entire lifecycle of a job, not just its result.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 20:28:20 +01:00
adam closed this issue 2025-12-29 20:28:20 +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: housekeeping
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#7798
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?