ANY.RUN: Bugfix - Fix type validation errors in get_intelligence action

[anyrun-integrations]

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:

• Testing of all the changes has been performed (for bug fixes / features)
• The manual_readme_content.md has been reviewed and added / updated if needed (for bug fixes / features)
• Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
• 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.
• Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
• 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
• 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)

• Fix type validation errors in get_intelligence action

What is the current behavior? (OPTIONAL)

• Action get_intelligence returns an error "Error in validating Threat Intelligence parameters. Error Message: '< param >' must be str, not < param_type >.", when any parameter with type other than 'string' is used.

What is the new behavior? (OPTIONAL)

• Action get_intelligence now performs type casting for all used parameters.

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 22 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]

@anyrun-integrations Static Tests results for commit 0213275 - https://drive.google.com/file/d/1-RxAUXM5Bx1-6UcfHZCkq6GRxNMaxZSu/view?usp=drivesdk

[splunk-soar-connectors-bot]

@anyrun-integrations Compile Tests results for commit 0213275 - https://drive.google.com/file/d/1hRxaWGfRRyY8DndHF_JTNHkagl27pk4C/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Static Tests results for commit 6af170f - https://drive.google.com/file/d/1FoNt-ouKVh9bL4gi4CnLWGyTx7bwxCy-/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Compile Tests results for commit 6af170f - https://drive.google.com/file/d/1ndimUNrVNB9MC66yn5nBKo0Sp7K_KR_D/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Static Tests results for commit cd919ca - https://drive.google.com/file/d/1us7FuYOKROLXKTpiv0ZLufIGCr2F_L65/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Static Tests results for commit 657de02 - https://drive.google.com/file/d/19gLb2gsU0IY4Xk2GQAxebgV71TRU1qNK/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Compile Tests results for commit 657de02 - https://drive.google.com/file/d/1rXtsHI0r_aYgsY4U6X4bLe5iBoVnPViu/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Static Tests results for commit 791af1d - https://drive.google.com/file/d/1kJUbJytXh-aSR-XkuXFl5_r-5aBCmL4q/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Compile Tests results for commit 791af1d - https://drive.google.com/file/d/1JIUnh4zOYHifB1OCEjXkjj2PqDdiAh23/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Static Tests results for commit 316b417 - https://drive.google.com/file/d/1Q1GWbIXeEEW_Rrbnf_7H4yjt-tx-uzu4/view?usp=drivesdk

[splunk-soar-connectors-bot]

@ishans-crest Compile Tests results for commit 316b417 - https://drive.google.com/file/d/1-Y3wa7hLtBgfuaDBiI68qaeA0j6s3bBL/view?usp=drivesdk

[ishans-crest]

Hi @anyrun-integrations,

We have made the necessary changes in the application code. One of the changes is upgrading the 'aiohttp' library version from 3.9.5 to 3.10.2. Let us know your feedback on this change.
Please test the application from your end and let us know the result.
Thank You.

[splunk-soar-connectors-bot]

@anyrun-integrations Static Tests results for commit 3b3a699 - https://drive.google.com/file/d/1JF0tdNN7CApvTU_p3Mbn9hOpvBvmL0TY/view?usp=drivesdk

[splunk-soar-connectors-bot]

@anyrun-integrations Compile Tests results for commit 3b3a699 - https://drive.google.com/file/d/1IRD_yKItNT8hLKloIHwP2hLP_J8rY7eY/view?usp=drivesdk

[anyrun-integrations]

Hello @ishans-crest,

We have updated 'anyrun-py' lib to work with aiohttp 3.10.2, otherwise every action would've failed with 'RuntimeError: no running event loop' error. After that no errors were encountered, so it should be good now.