Recorded Future for Splunk SOAR 4.3.2 - Bug fixes - Alert Polling

[JQvickWester]

Please ensure your pull request (PR) adheres to the following guidelines:

• Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist

Please check if your PR fulfills the following requirements:

• [X] Testing of all the changes has been performed (for bug fixes / features)
• [X] The manual_readme_content.md has been reviewed and added / updated if needed (for bug fixes / features)
• [X] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
• [X] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
• [ ] Verify all checks are passing.
• [X] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
• [X] Do NOT submit updates to dependencies unless it fixes an issue.

  Pull Request Type

Please check the type of change your PR introduces:

• [ ] New App
• [X] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Documentation
• [ ] Other (please describe):

Security Considerations (REQUIRED)

• [ ] If you are exposing any endpoints using a REST handler, please document them in the manual_readme_content.md.
• [ ] If this is a new connector or you are adding new actions
  • [ ] Please document in the manual_readme_content.md all methods (eg, OAuth) used to authenticate with the service that the connector is integrating with.
  • [ ] If any actions are unable to run on SOAR Cloud, please document this in the manual_readme_content.md.
• [ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
• [ ] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through the Vault API.
• [ ] Are you are marking code to be ignored by Semgrep with nosemgrep? If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Bug fixes:

• Changes to polling of alerts; now requires a comma seperated list to pull in alerts.
• Fixing logic issue blocking the polling of alerts under certain conditions.
• Fixing issues with hardcoded vault path for Cloud, instead using Vault class to get appropriate tmp vault path.

What is the current behavior? (OPTIONAL)

• Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

• Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

• Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

• Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

---

Thanks for contributing!

[splunk-soar-connectors-bot]

Thank you for your submission! We have a total of 19 PRs open right now, and we are working hard on all of them! We will take a look as soon as we can.

[splunk-soar-connectors-bot]

@JQvickWester Static Tests results for commit d81cdc85c9b45299ac5e13dd7eea9d76095b27ac - https://drive.google.com/file/d/1theWo2lwYCmlWb58XvFbStbMt0wAxctG/view?usp=drivesdk

[splunk-soar-connectors-bot]

@JQvickWester Compile Tests results for commit d81cdc85c9b45299ac5e13dd7eea9d76095b27ac - https://drive.google.com/file/d/1CiZSdxUIM14EeXSRtSJp8HNUOa357Jh2/view?usp=drivesdk