Xsup 67244/update crypto docker

[shmuel44]

Related Issues

related: https://jira-dc.paloaltonetworks.com/browse/XSUP-67244

Description

[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/CommonScripts/Scripts/CertificateExtract
CertificateExtract.py	134	32	76%	44–46, 48–50, 87–90, 92, 135, 138, 162, 179–180, 188, 207, 212, 374–375, 377–378, 386, 394, 468, 471, 477, 496–499
Packs/CommonScripts/Scripts/PFXAnalyzer
PFXAnalyzer.py	180	122	32%	34–37, 42–46, 48–49, 55–56, 63, 65–69, 98, 100–102, 104–112, 124–129, 131, 144–151, 156–166, 168, 170–174, 179–182, 187–188, 190, 192–196, 213, 218, 220, 226–230, 232–233, 235–238, 240–248, 250–253, 255–256, 259, 272–273, 275, 277–278, 280–281, 283, 285–286, 288, 298, 304, 319, 329–330
Packs/Microsoft365Defender/Scripts/MS365DefenderAddComment
MS365DefenderAddComment.py	22	6	72%	23, 36–38, 40–41
Packs/MicrosoftCloudAppSecurity/Integrations/MicrosoftCloudAppSecurity
MicrosoftCloudAppSecurity.py	381	20	94%	127–130, 139–140, 236, 252–253, 261–262, 267, 269, 341, 347, 752, 756–758, 796
Packs/MicrosoftGraphAPI/Integrations/MicrosoftGraphAPI
MicrosoftGraphAPI.py	47	2	95%	110–111
Packs/MicrosoftGraphSecurity/Integrations/MicrosoftGraphSecurity
MicrosoftGraphSecurity.py	1124	325	71%	101–102, 105, 108–109, 112–114, 117–119, 122–123, 126–128, 131–133, 136–138, 141–144, 147–148, 162–163, 166–167, 170–171, 174–175, 178–179, 182–183, 186–189, 192–193, 198–199, 212, 216–217, 222, 225–228, 231–233, 236–237, 243, 257–260, 263–264, 267–269, 272–274, 276–278, 280, 290–292, 295, 297, 300–301, 322–323, 328, 345–346, 372–373, 377, 400–403, 420–421, 438–441, 458–459, 492–493, 503–504, 515, 522, 525, 528, 533, 538, 545, 548, 555, 558, 564, 567–569, 574–579, 581, 598, 620–621, 660, 670, 673, 687, 713–716, 740–741, 743, 747, 817, 825–828, 830–831, 844, 872, 1091, 1123, 1161–1168, 1204–1208, 1363, 1387–1389, 1396–1397, 1402–1405, 1434, 1437, 1448–1450, 1459–1460, 1465–1473, 1478–1486, 1491–1495, 1500–1508, 1525–1527, 1530–1531, 1536–1544, 1561–1575, 1579, 1594–1600, 1633–1634, 1675, 1678, 1682–1683, 1703–1704, 1708–1709, 1717, 1726, 1735, 1745, 1754–1757, 1761, 1765, 1782, 1784, 1894, 1903–1904, 1907–1908, 1919, 1994, 2068, 2115, 2200, 2208, 2216, 2240–2241, 2452, 2522–2524, 2526, 2563, 2596, 2629, 2660, 2673, 2681, 2725–2726, 2730–2731, 2805–2810, 2818, 2820, 2822, 2824, 2826, 2828, 2830, 2832, 2834, 2838, 2841, 2846–2847
TOTAL	1888	507	73%

Tests	Skipped	Failures	Errors	Time
105	0 💤	0 ❌	0 🔥	3.274s ⏱️

[marketplace-ai-reviewer]

🤖 Analysis started. Please wait for results...

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

Thanks for your contribution to the Microsoft integrations! I've reviewed your changes and noticed a few recurring structural and metadata issues across the updated packs.

Please ensure that name or display is the very first key in your YAML files, verify that you are using the latest demisto/crypto Docker image, and update the pack metadata files to include "Microsoft" in the keywords and the missing created key.

Let me know if you have any questions while making these updates!

Additionally, please address the following file-level notes:

• Packs/MicrosoftCloudAppSecurity/Integrations/MicrosoftCloudAppSecurity/MicrosoftCloudAppSecurity.yml: CRITICAL: The first key defined at the root level of the .yml file must always be name or display. Currently, the file starts with category. Please reorder the keys so that name or display is at the very top.
• Packs/MicrosoftGraphAPI/Integrations/MicrosoftGraphAPI/MicrosoftGraphAPI.yml: CRITICAL: The first key defined at the root level of the .yml file must always be name or display. Currently, the file starts with category. Please reorder the keys so that name or display is at the very top.
• Packs/MicrosoftGraphSecurity/Integrations/MicrosoftGraphSecurity/MicrosoftGraphSecurity.yml: CRITICAL: The first key defined at the root level of the .yml file must always be name or display. Currently, the file starts with category. Please reorder the keys so that name or display is at the very top.
• Packs/Microsoft365Defender/pack_metadata.json: The mandatory key created is missing from the pack metadata. Please add it.
• Packs/MicrosoftCloudAppSecurity/pack_metadata.json: The vendor name (Microsoft) must appear in the keywords list. Please add it.
• Packs/MicrosoftGraphAPI/pack_metadata.json: The vendor name (Microsoft) must appear in the keywords list. Please add it.
• Packs/MicrosoftGraphSecurity/pack_metadata.json: The vendor name (Microsoft) must appear in the keywords list. Please add it.

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

[content-bot]

This PR was automatically updated by a GitHub Action

• CommonScripts pack version was bumped to 1.22.5.

To stop automatic version bumps, add the ignore-auto-bump-version label to the github PR.

[content-bot]

This PR was automatically updated by a GitHub Action

• CommonScripts pack version was bumped to 1.22.6.

To stop automatic version bumps, add the ignore-auto-bump-version label to the github PR.

[content-bot]

This PR was automatically updated by a GitHub Action

• CommonScripts pack version was bumped to 1.22.7.

To stop automatic version bumps, add the ignore-auto-bump-version label to the github PR.

[content-bot]

Validate summary
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: fe55c116020956f5

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

⚠️ AI-generated triage. Validate before acting.

[BEAdi]

Force merge - 1 test playbook is failing with the same error as here, on a PR with no change (#44183)