Add rawJSON to fetched indicator object in Feed MISP Threat Actors

[iamtimroberts]

Added rawJSON to fetched indicator object in Feed MISP Threat Actors to enable custom mapping.

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Related Issues

fixes: N/A

Description

Currently unable to build a custom mapper for this Feed Integration due to the rawJSON not being returned. This causes no data to be returned in the Classifier/Mapper editors when you pull from this instance. The simple addition of 'rawJSON': threat_actor to the returned indicators object from fetch_indicators_command allows the Classifier/Mapper editors to actually fetch data to build the mapper off of.

Must have

• [x ] Tests
• [ x] Documentation

[CLAassistant]

All committers have signed the CLA.

[content-bot]

Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @mmhw will know the proposed changes are ready to be reviewed.
For your convenience, here is a link to the contributions SLAs document.

[content-bot]

Hi @iamtimroberts, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link.

[MLainer1]

Looks good from my standpoint

[mmhw]

Hi @iamtimroberts,
Thank you for your contribution!
Good work :)

[mmhw]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@iamtimroberts, Please be sure to sign here.

[iamtimroberts]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@iamtimroberts, Please be sure to sign here.

I've already filled that out - when I click the link it shows I've already signed it.

[mmhw]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@iamtimroberts, Please be sure to sign here.

I've already filled that out - when I click the link it shows I've already signed it.

Hi @iamtimroberts,
Did you sign here? https://cla-assistant.io/demisto/content?pullRequest=39599

[iamtimroberts]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@iamtimroberts, Please be sure to sign here.

I've already filled that out - when I click the link it shows I've already signed it.

Hi @iamtimroberts, Did you sign here? https://cla-assistant.io/demisto/content?pullRequest=39599

Yup - its showing signed:

[mmhw]

Hi @iamtimroberts, Please note that I sent you an email.

[iamtimroberts]

I didn't realize that the commit was from my corporate palo alto account so that was the discrepancy with the CLA. It is now signed.

[github-actions]

Thank you for your contribution. Your external PR has been merged and the changes are now included in an internal PR for further review. The internal PR will be merged to the master branch within 3 business days.