Feature/jobs rest api#10801
Open
andrewfallin-pnnl wants to merge 4 commits into
Open
Conversation
Feeds now store the ID of their most recent background job. The job ID is included in the fetch-feed queued message so API callers know which job to poll. Adds GET /jobs/view/:id REST endpoint to query job status and progress without scraping the UI. Moves the job status converter out of Job model into JobsController where it belongs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does it do?
A Job ID in MISP uniquely identifies a background job process. The most recent Job ID was previously unavailable to PyMISP Feeds API or exposed as an API endpoint for Job retrieval. This work exposes Jobs as an API endpoint for MISP and PyMISP so that we can track when feeds are running, waiting, errored, or completed.
Questions