Skip to content
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

randomizerxd
Copy link
Contributor

@randomizerxd randomizerxd commented May 17, 2023

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: 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

  • 6.0.0
  • 6.1.0
  • 6.2.0
  • 6.5.0

Does it break backward compatibility?

  • Yes
    • Further details:
  • No

Must have

  • Tests
  • Documentation

@thefrieddan1
Copy link
Contributor

Hi @randomizerxd ,
Thank you for your contribution,
in order for me to start reviewing please be sure to fill the Contribution Registration.
Also please mind you didnt bump the packs version also please add ReleaseNotes for the new version.

Thanks

@randomizerxd
Copy link
Contributor Author

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
@thefrieddan1 thefrieddan1 added Community Partner Support Level Indicates that the contribution is for Partner supported pack and removed Community Partner labels May 21, 2023
@thefrieddan1
Copy link
Contributor

Hi @randomizerxd,

Thanks for filling the Contribution Registration.
Please update the version and Release Notes.
You can see how to in the following link from the failed ci/circleci: run validations step in the PR:
https://app.circleci.com/pipelines/github/demisto/content/261045/workflows/d87599a9-edf0-44c8-bd34-5c1c9a290485/jobs/701541

@thefrieddan1 thefrieddan1 added the pending-contributor The PR is pending the response of its creator label May 22, 2023
@randomizerxd
Copy link
Contributor Author

I have already updated the version and release notes. I manually created 1_5_3.md and updated currentVersion to 1.5.3.

@thefrieddan1
Copy link
Contributor

@randomizerxd verion 1.5.3 is already in master,
I have bumped the version to 1.5.4 with your changes.

@efelmandar
Copy link
Contributor

@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 Recorded Future URL Reputation and Recorded Future URL Intelligence I observed the removal of the scriptarguments section. Could you kindly explain the reasoning behind this change?

@randomizerxd
Copy link
Contributor Author

randomizerxd commented May 26, 2023

Thanks Erez (@efelmandar)! Sure. From my understanding, the scriptarguments section is not needed for those two conditional tasks. It contains inputs.url but the playbook input is URL. The conditions section exists which contains inputs.URL. Do you know why the scriptarguments section is there?

@efelmandar
Copy link
Contributor

@randomizerxd Following our conversation I approve the PR - @thefrieddan1 FYI

@thefrieddan1 thefrieddan1 added ready-for-instance-test In contribution PRs, this label will cause a trigger of a build with a modified pack from the PR. and removed pending-contributor The PR is pending the response of its creator labels May 28, 2023
@thefrieddan1 thefrieddan1 merged commit f97aca5 into demisto:contrib/randomizerxd_randomizerxd-Recorded-Future-Playbooks May 28, 2023
thefrieddan1 added a commit that referenced this pull request May 30, 2023
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community Contribution Form Filled Whether contribution form filled or not. Contribution Thank you! Contributions are always welcome! docs-approved Partner Support Level Indicates that the contribution is for Partner supported pack ready-for-instance-test In contribution PRs, this label will cause a trigger of a build with a modified pack from the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants