AlienVault - Add HTTP-500 Handling

[TheL0L]

Related Issues

fixes: XSUP-70537

Description

Add http-500 error handling.

[content-bot]

🤖 AI-Powered Code Review Available

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

Available Commands:

• @marketplace-ai-reviewer start review - Initiate a full AI code review
• @marketplace-ai-reviewer re-review - Incremental review for new commits

[marketplace-ai-reviewer]

🤖 Analysis started. Please wait for results...

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
Packs/AlienVault_OTX/Integrations/AlienVault_OTX_v2
AlienVault_OTX_v2.py	338	84	75%	61, 78, 82, 86, 93–94, 99, 112–113, 120, 183, 189, 200, 301, 372–375, 455, 518, 524, 614, 702, 717–720, 735, 742, 744, 758–761, 777, 779, 781, 813, 854, 896, 910–913, 918, 925, 927, 941–944, 955, 957, 959, 966, 968–978, 980–981, 983, 996–998, 1011–1017, 1019–1020, 1022–1024
TOTAL	338	84	75%

Tests	Skipped	Failures	Errors	Time
28	0 💤	0 ❌	0 🔥	3.097s ⏱️

[marketplace-ai-reviewer]

🤖 AI Review Disclaimer

This review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause.

[marketplace-ai-reviewer]

Hi! Thanks for your contribution to the AlienVault OTX pack. The updates look solid, but I left a few minor suggestions to align the code with our current standards. Specifically, please update the Client class to inherit from ContentClient, consolidate the 500/504 error handling logic to reduce duplication, and make a few quick formatting tweaks to the release notes and pack keywords. Thanks again for your hard work on this!

Additionally, please address the following file-level notes:

• Packs/AlienVault_OTX/Integrations/AlienVault_OTX_v2/AlienVault_OTX_v2.py: Update Client class inheritance to use ContentClient.
• Packs/AlienVault_OTX/pack_metadata.json: The vendor name 'AlienVault' must appear in the keywords list.

@kamalq97, @TheL0L please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

[content-bot]

Validate summary
The following errors were reported as warnings: MC101, RM108, PB131, PB130.
The following errors were thrown as a part of this pr: .
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

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

[content-bot]

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: failed
Report ID: 47a0f3f6fb1fd298

📋 Triage Report
💡 Resolutions are available in the full report.

⚠️ AI-generated triage. Validate before acting.