-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify RF Playbooks: Check for "Recorded Future v2" instead of "Recorded Future" integration instance #26589
Conversation
Hi @randomizerxd , Thanks |
Sorry I thought I had already filled it out. I just completed it. |
…ooks' into randomizerxd-Recorded-Future-Playbooks
playbook currently fails when no RF results are returned
playbook currently fails when no RF results are returned
playbook currently fails when no RF results are returned
playbook currently fails when no RF results are returned
playbook currently fails when no RF results are returned
playbook currently fails when no RF results are returned
playbook currently fails when no RF results are returned
playbook currently fails when no RF results are returned
…ooks' into randomizerxd-Recorded-Future-Playbooks
Hi @randomizerxd, Thanks for filling the Contribution Registration. |
I have already updated the version and release notes. I manually created 1_5_3.md and updated currentVersion to 1.5.3. |
@randomizerxd verion 1.5.3 is already in master, |
@randomizerxd Thank you for your time and effort in making this contribution. I have reviewed your changes and I must say, you've done an excellent job! There is just one thing I noticed that I would like to bring up with you. In the playbooks |
Thanks Erez (@efelmandar)! Sure. From my understanding, the |
@randomizerxd Following our conversation I approve the PR - @thefrieddan1 FYI |
f97aca5
into
demisto:contrib/randomizerxd_randomizerxd-Recorded-Future-Playbooks
…ded Future" integration instance (#26589) (#27020) * Update playbook-Recorded_Future_CVE_Reputation.yml * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Create 1_5_3.md * update currentVersion to 1.5.3 * scriptarguments inputs.url not needed * scriptarguments inputs.url not needed * ${inputs.URL} instead of ${RecordedFuture.URL.name} playbook currently fails when no RF results are returned * ${inputs.URL} instead of ${RecordedFuture.URL.name} playbook currently fails when no RF results are returned * ${inputs.CVE} instead of ${RecordedFuture.CVE.name} playbook currently fails when no RF results are returned * ${inputs.CVE} instead of ${RecordedFuture.CVE.name} playbook currently fails when no RF results are returned * ${inputs.Domain} instead of ${RecordedFuture.Domain.name} playbook currently fails when no RF results are returned * ${inputs.Domain} instead of ${RecordedFuture.Domain.name} playbook currently fails when no RF results are returned * ${inputs.IP} instead of ${RecordedFuture.IP.name} playbook currently fails when no RF results are returned * ${inputs.IP} instead of ${RecordedFuture.IP.name} playbook currently fails when no RF results are returned * Bump version --------- Co-authored-by: Randy Baldwin <32545292+randomizerxd@users.noreply.github.com> Co-authored-by: Danny_Fried <dfried@paloaltonetworks.com>
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
Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer
Minimum version of Cortex XSOAR
Does it break backward compatibility?
Must have