Recorded Future for Splunk SOAR: Bug-fix - Release of app version 4.3.2

JQvickWester commented 5 months ago

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.
[x] 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)
[x] Documentation
[x] Other (please describe): Copyright notice date update

Security Considerations (REQUIRED)

[x] 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:
[x] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through the Vault API.
[x] 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. API key fingerprint is logged for debugging purposes.

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

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.
Improved visibility of support documents
Renaming of app headers
Fixing issues with hardcoded path for Cloud
Improved format for Intelligence Command Widgets
Added status config options for fetching standard and playbook alerts

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 commented 5 months ago

Thank you for your submission! We have a total of 16 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 commented 5 months ago

@JQvickWester Static Tests results for commit f22a48483082e749b4644969196d22158b97521f - https://drive.google.com/file/d/1MfHu-f1w-nKBPx0feWykTkyOqvGkggtv/view?usp=drivesdk

splunk-soar-connectors-bot commented 5 months ago

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

splunk-soar-connectors-bot commented 5 months ago

@JQvickWester Static Tests results for commit 88a996b68408391249631cba0a4f72187a7b4663 - https://drive.google.com/file/d/1xwXYWU5Hi-uoA6fZL9kDXFV7FbHQH9k-/view?usp=drivesdk

splunk-soar-connectors-bot commented 5 months ago

@JQvickWester Compile Tests results for commit 88a996b68408391249631cba0a4f72187a7b4663 - https://drive.google.com/file/d/1jD6czO5-F8SWXN3rSAl8V_Sl55DJ7Ccy/view?usp=drivesdk

splunk-soar-connectors-bot commented 5 months ago

@JQvickWester Static Tests results for commit 8f365d367823fe15d70b66c3a37c308a7eaac80a - https://drive.google.com/file/d/18GNx4f1E0MZBgrRZXuyp-BjEL0uMWm2T/view?usp=drivesdk

splunk-soar-connectors-bot commented 5 months ago

@JQvickWester Compile Tests results for commit 8f365d367823fe15d70b66c3a37c308a7eaac80a - https://drive.google.com/file/d/1oOjnQqhmH350OStyThDqayTl-l9LiCnI/view?usp=drivesdk

JQvickWester commented 5 months ago

Hi @dhwanis-crest

Looking to get this merged, but I'm a bit confused about the AWS CodeBuild us-west-2 (prodsec-scans) action that appears to be failing. Clicking details redirect me to an AWS login page.

@nestoor22 suggested that I reach out to you.

Do you have any more details as to why this is failing?

Thanks!

bb-splunk commented 5 months ago

The prodsec fail is caused by requests package, please remove it from requirements, as it is supplied by SOAR platform @JQvickWester

splunk-soar-connectors-bot commented 5 months ago

@JQvickWester Static Tests results for commit 8efa1d5cb00f1ba16a6d1034811a702a3792841a - https://drive.google.com/file/d/1NNix-1BruPQvr5ZiBhIXcMNUYstmnKdz/view?usp=drivesdk

splunk-soar-connectors-bot commented 5 months ago

@JQvickWester Compile Tests results for commit 8efa1d5cb00f1ba16a6d1034811a702a3792841a - https://drive.google.com/file/d/1_x84k78mbjySh0oXPBkIG9IHx2y-QIzb/view?usp=drivesdk

JQvickWester commented 5 months ago

@bb-splunk Thank you for you assistance, that cleared it up - have a great day!

@nestoor22 looks like this is ready to merge, if you'd be so kind!

splunk-soar-connectors / recordedfuture