Add FireEye HX triage commands

[content-bot]

Original External PR

external pull request

Contributor

@mcvic1rj

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Related Issues

N/a

Description

This PR adds 5 new commands, utilized to create, delete, get, and download triage requests for an HX Server.
Commands:

• fireeye-hx-triage-acquistion-delete -> Deletes a specified Triage collection.
• fireeye-hx-triage-acquistition-package-get -> Downloads the package(mans) for a specified Triage collection.
• fireeye-hx-triage-acquistition-get -> Gets status/info on a Triage collection.
• fireeye-hx-triage-acquistition-start -> Starts a Triage collection for a specified host.
• fireeye-hx-host-acquisitions-list -> Returns a list of all acquisitions for a specified host, across different types.

Must have

• Tests
• Documentation

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

[content-bot]

🤖 AI-Powered Code Review Available

Hi @kamalq97, 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

[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

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
Packs/FireEyeHX/Integrations/FireEyeHXv2
FireEyeHXv2.py	1209	329	72%	255, 258–261, 267–271, 274, 281, 283, 290, 292, 295, 298, 301, 310, 326, 339–340, 342, 345–346, 353, 359, 364, 367, 369, 376, 379, 381, 384, 386, 389, 391, 394, 396, 422, 425, 428, 431, 434, 438, 441, 459, 471, 483, 495, 503–504, 522–523, 529, 558, 572–575, 577–578, 583, 586, 595, 605–609, 611, 614–615, 621–623, 632, 634–635, 637–638, 640–642, 645–646, 661–662, 664–666, 717, 722, 724–725, 727–728, 730, 733, 745, 748, 754, 817, 820, 848–849, 865, 966, 973, 980, 984, 995, 1024, 1029, 1041, 1044, 1087, 1089, 1091, 1093, 1148–1151, 1157–1158, 1160–1162, 1164, 1168–1169, 1179, 1267, 1284, 1299, 1309, 1421–1423, 1455, 1493–1494, 1509, 1527–1529, 1531, 1549–1551, 1553, 1571–1573, 1575, 1594–1601, 1603–1604, 1618–1619, 1629–1636, 1638–1639, 1668–1673, 1675–1676, 1707–1714, 1716–1717, 1754, 1760, 1762–1764, 1767, 1769, 1783, 1785, 1825, 1831, 1833, 1835–1837, 1839, 1876, 1896, 1909, 1912, 1915, 1917, 1930–1931, 1934, 2106, 2125, 2198, 2207, 2215–2216, 2218–2219, 2221, 2223–2226, 2228, 2237–2239, 2241, 2251, 2253–2257, 2259, 2262, 2363–2364, 2378, 2382, 2384, 2418, 2436, 2438, 2440, 2444, 2466–2470, 2496, 2538–2539, 2541–2545, 2555–2557, 2566, 2592–2593, 2650, 2672–2673, 2677, 2750–2759, 2763, 2765–2767, 2780, 2786, 2831–2835, 2838–2840, 2845, 2849–2852, 2854–2856, 2858–2866, 2868–2871, 2874–2875, 2878–2879
TOTAL	1209	329	72%

Tests	Skipped	Failures	Errors	Time
152	0 💤	0 ❌	0 🔥	3.318s ⏱️

[content-bot]

Validate summary
The following errors were reported as warnings: PB131, PB130, RM108.
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? ✅