Skip to content

removed agentix from integration where both fetch incidents and fetch events#43744

Open
Shir2611 wants to merge 1 commit intomasterfrom
remove-agentix-from-event-collectors-part-1
Open

removed agentix from integration where both fetch incidents and fetch events#43744
Shir2611 wants to merge 1 commit intomasterfrom
remove-agentix-from-event-collectors-part-1

Conversation

@Shir2611
Copy link
Copy Markdown
Contributor

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

fixes: CIAC-15886

Description

removed agentix from integrations where both fetch incidents and fetch events

Must have

  • Tests
  • Documentation

@Shir2611 Shir2611 requested review from BEAdi and jbabazadeh March 30, 2026 12:56
@Shir2611 Shir2611 self-assigned this Mar 30, 2026
@Shir2611 Shir2611 added docs-approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. labels Mar 30, 2026
@content-bot
Copy link
Copy Markdown
Contributor

🤖 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 marketplace-ai-reviewer removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Mar 30, 2026
@marketplace-ai-reviewer
Copy link
Copy Markdown
Contributor

🤖 Analysis started. Please wait for results...

@github-actions
Copy link
Copy Markdown

Coverage

Tests Skipped Failures Errors Time
603 0 💤 0 ❌ 0 🔥 22.802s ⏱️

@marketplace-ai-reviewer
Copy link
Copy Markdown
Contributor

🤖 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.

Copy link
Copy Markdown
Contributor

@marketplace-ai-reviewer marketplace-ai-reviewer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi there, thanks for your contribution! I've reviewed the changes and noticed a few missing details across the pack metadata files. Specifically, please ensure the vendor and pack names are added to the keywords lists, include missing mandatory fields like created and githubUser, and refine the pack description to be a more concise summary. Thanks again for your work on this!

Additionally, please address the following file-level notes:

  • Packs/ExabeamSecurityOperationsPlatform/pack_metadata.json: - Add the vendor name to the keywords list.
  • Add the mandatory created key to the pack metadata.
  • Rewrite the description to be a concise, high-level summary of the pack's purpose.
  • Packs/HelloWorld/pack_metadata.json: - Add the vendor/pack name to the keywords list.
  • Add the githubUser field with a list of valid GitHub usernames.

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

@content-bot
Copy link
Copy Markdown
Contributor

Validate summary
The following errors were thrown as a part of this pr: DO106, BA125.
The following errors can be ignored: BA125.
The following errors cannot be ignored: DO106.
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: DO106, BA125.

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

docs-approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants