Playbook support

[pranjalg1331]

Description

Closes #60
Methods Added

• GetPlaybookByName
• ListPlaybooks
• CreateObservablePlaybookAnalysis
• CreateFilePlaybookAnalysis

Issues

add the related issue(s) your change tackles

Type of change

list down the type of change

• Bug fix
• [x ] New feature (added a new endpoint or created)
• Breaking fix (a bug fix or new feature that would cause exisiting functionality not to work as expected)

Checklist

• [ x] if a new feature was added it passed all its (if made) test cases
• if a bug fix was added it passed all its existing test cases

Important Rules

• If your changes decrease the overall tests coverage (you will know after the Codecov CI job is done), you should add the required tests to fix the problem
• Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review

Please delete if the PR is for bug fixing.

[pranjalg1331]

@drosetti Please review

[mlodic]

thanks for the PR. Can you provide an example of a successful run of the new APIs against a local IntelOwl instance?

[mlodic]

also, there are linter errors to be fixed

[pranjalg1331]

CreateFilePlaybookAnalysis- Response

CreateObservablePlaybookAnalysis- Response

GetPlaybookByName- Response

[pranjalg1331]

@mlodic, I have solved the golangci-lint errors.
Should I also include somewhere the usage of playbook methods, possibly creating more sample example files or in docs?

[mlodic]

I have solved the golangci-lint errors.

Great!

Should I also include somewhere the usage of playbook methods, possibly creating more sample example files or in docs?

Any documentation or tutorial is always appreciated, that's really the best benefit you can do to the community. Feel free to do that.

[pranjalg1331]

@mlodic I have added an example for analyzing files with a playbook. It should give an overview on usage of rest of the functions. Please review.

[pranjalg1331]

@mlodic Please review

[pranjalg1331]

@mlodic Please review

[mlodic]

please do not tag us repetitively. Be respectful and use tags only when strictly needed. We have a life and we help here in our free time.

Plus, please ask reviews by using the builtin way in Github (click and select on the top right of the PR). No need to ask it more than once. Patience.

[pranjalg1331]

Apologies if I overstepped. I really appreciate the time you and others put into reviewing contributions. I'll make sure to follow the guidelines and be patient moving forward.

[mlodic]

Thank you for your understanding. Can you pull the changes that I have just merged from your other PR #71 here? So we can re-run the CI with those additional checks and then merge it.

[pranjalg1331]

I have updated the branch to run all the ci tests.

[mlodic]

great