Skip to content

Updated the user-agent of PolySwarmV2 requests.#43084

Open
content-bot wants to merge 2 commits intomasterfrom
contrib/polyswarm_fix/polyswarmv2-useragent
Open

Updated the user-agent of PolySwarmV2 requests.#43084
content-bot wants to merge 2 commits intomasterfrom
contrib/polyswarm_fix/polyswarmv2-useragent

Conversation

@content-bot
Copy link
Contributor

Original External PR

external pull request

Contributor

@alanjds

They now identify xsoar and the plugin version,
making easier to fix issues and identify regressions.

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

Must have

  • Tests
  • Documentation

fixes: https://jira-dc.paloaltonetworks.com/browse/CIAC-15812

* Updated the user-agent of PolySwarmV2 requests.

They now identify xsoar and the plugin version,
making easier to fix issues and identify regressions.

* Allow current & upcoming version of polyswarm_api

Newer versions will default the user-agent to have
`polyswarm_api` instead of `polyswarm-api`
@content-bot content-bot added Contribution Thank you! Contributions are always welcome! docs-approved Partner Contribution Form Filled Whether contribution form filled or not. Partner Support Level Indicates that the contribution is for Partner supported pack Internal PR Partner-Approved Pending-Partner ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines labels Feb 12, 2026
@content-bot content-bot requested a review from kamalq97 February 12, 2026 16:33
@content-bot
Copy link
Contributor Author

🤖 AI-Powered Code Review Available

Hi @kamalq97, you can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @content-bot start review - Initiate a full AI code review
  • @content-bot re-review - Incremental review for new commits

@content-bot
Copy link
Contributor Author

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @content-bot start review - Initiate a full AI code review
  • @content-bot re-review - Incremental review for new commits

@github-actions
Copy link

github-actions bot commented Feb 12, 2026

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/PolySwarm/Integrations/PolySwarmV2
   PolySwarmV2.py1996368%19, 21, 61, 63–69, 71, 76, 81–82, 95, 98, 139–140, 154–155, 162–163, 183–184, 199–200, 221–222, 230, 240–241, 253–255, 291–293, 295–296, 298–300, 302–320, 322–323
TOTAL1996368% 

Tests Skipped Failures Errors Time
8 0 💤 0 ❌ 0 🔥 1m 49s ⏱️

@kamalq97 kamalq97 enabled auto-merge (squash) February 12, 2026 16:55
@content-bot
Copy link
Contributor Author

Validate summary
The following errors were thrown as a part of this pr: RN111.
The following errors cannot be ignored: RN111.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: RN111.

Verdict: PR can be force merged from validate perspective? ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Contribution Form Filled Whether contribution form filled or not. Contribution Thank you! Contributions are always welcome! docs-approved Internal PR Partner Support Level Indicates that the contribution is for Partner supported pack Partner Partner-Approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines skip-ai-review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants