Skip to content
This repository was archived by the owner on Sep 20, 2023. It is now read-only.

Cortex job api documentation #11

Merged
merged 5 commits into from
Sep 22, 2017
Merged

Cortex job api documentation #11

merged 5 commits into from
Sep 22, 2017

Conversation

srilumpa
Copy link
Contributor

The documentation was not explaining how we could interact with the API to trigger Cortex jobs. I wrote a few lines about Cortex jobs and how to create one (in fact, only the part that I tested) and I set a base structure for future documentation about connectors.

I hope this is to your liking.

This closes TheHive-Project/TheHive#308.


Required attributes:
- `analyzerId` (string): identifier of the analyzer used by the job
- `status` (enumeration): status of the job (`InProgress`, `Success`, `Failure`) **default=`InProgress`**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an internal field managed by the backend. It's be better to list it under a Attributes generated by the backend section.

@nadouani
Copy link
Contributor

Thanks @srilumpa this is very clean, good work. I'll let @To-om review and merge the PR.

@nadouani nadouani requested a review from To-om September 20, 2017 08:33
@To-om To-om merged commit 5969d5c into TheHive-Project:master Sep 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Run observable analyzers through API
3 participants