Skip to content

Re-enable get-modified-remote-data command#44530

Open
MosheEichler wants to merge 1 commit into
masterfrom
fix/XSOAR-MIRROR/Re-enable-get-modified-remote-data
Open

Re-enable get-modified-remote-data command#44530
MosheEichler wants to merge 1 commit into
masterfrom
fix/XSOAR-MIRROR/Re-enable-get-modified-remote-data

Conversation

@MosheEichler
Copy link
Copy Markdown
Contributor

Status

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

Related Issues

Description

Added the get-modified-remote-data command

Must have

  • Tests
  • Documentation

@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

@MosheEichler MosheEichler self-assigned this Jun 4, 2026
@MosheEichler MosheEichler added the release-notes-only Indicates that this pull request has ONLY release notes to review for documentation process label Jun 4, 2026
@MosheEichler MosheEichler added the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Jun 4, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 4, 2026

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/XSOARmirroring/Integrations/XSOARmirroring
   XSOARmirroring.py36715458%67, 78, 81, 84, 106, 109, 136, 141, 148–150, 152–153, 159–161, 167–169, 230–233, 235, 237–238, 242–243, 245, 247–248, 250–251, 271–276, 278, 352, 359, 410, 419–425, 427, 467–472, 474–477, 479, 481, 507–509, 511–516, 518–520, 522–523, 525, 527, 536, 540, 596–597, 601, 607–608, 610, 630–633, 638–639, 641–642, 644, 646, 651, 657, 660, 663–672, 680–684, 687, 690–696, 698, 700, 712–714, 726, 728–730, 732–733, 735–736, 738–740, 742, 788, 791, 798, 803–807, 811–812, 865–866, 872, 900
TOTAL36715458% 

Tests Skipped Failures Errors Time
31 0 💤 0 ❌ 0 🔥 2.715s ⏱️

@content-bot
Copy link
Copy Markdown
Contributor

⚠️ The PR is missing the ready-for-pipeline-running label. Please add the label when the PR is ready in order to proceed.

@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 Jun 4, 2026
@marketplace-ai-reviewer
Copy link
Copy Markdown
Contributor

🤖 Analysis started. Please wait for results...

@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 contributing this new command to the XSOAR mirroring integration. I've left a few notes to help polish the PR before we can get it merged.

The most important item is that adding a new command requires a minor version bump (2.2.0) rather than a patch. You'll also need to update the README to include command examples, standard phrasing, and snake_case arguments for the new command—running demisto-sdk generate-docs should help automate much of this formatting. Lastly, please remember to add relevant vendor keywords to the pack metadata.

Thanks again for the great work on this!

Additionally, please address the following file-level notes:

  • Packs/XSOARmirroring/pack_metadata.json: The keywords list is currently empty. Please add the vendor's name (e.g., Cortex or XSOAR) to the keywords list.
  • Packs/XSOARmirroring/ReleaseNotes/2_1_3.md: The release notes describe the addition of a new command, which is a feature addition. According to semantic versioning rules, this requires a minor bump (e.g., 2.2.0) rather than a patch bump (2.1.3). Please update the version in pack_metadata.json and rename this file to 2_2_0.md. You can use demisto-sdk update-release-notes -i Packs/XSOARmirroring -u minor to automate this. Refer to the Release Notes Documentation.

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

***
Returns a list of incident IDs that were modified since the last sync. Used to enable incremental mirroring and avoid full blind syncs.

> **Note:** This command is supported only for Cortex XSOAR version 8.14 and later.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please confirm if this command is also applicable to Cortex XSIAM. If it is, consider updating this note to include Cortex XSIAM (e.g., 'supported only for Cortex XSOAR and Cortex XSIAM version 8.14 and later').


#### Base Command

`get-modified-remote-data`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The Command example section is missing for this command. According to the Command Examples - Integration Documentation guidelines, every command should have a command example with real CLI syntax.

Please add a #### Command example section (e.g., !get-modified-remote-data lastUpdate="2023-01-01T00:00:00Z") and consider regenerating the README using demisto-sdk generate-docs.


#### Context Output

There is no context output for this command.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The standard SDK-generated phrasing for commands without context outputs is 'There are no context outputs for this command.' Please update this phrasing.

We recommend using demisto-sdk generate-docs to ensure all standard sections (like Human Readable Output) are included and formatted correctly. See Creating Documentation.

Suggested change
There is no context output for this command.
There are no context outputs for this command.

### get-modified-remote-data

***
Returns a list of incident IDs that were modified since the last sync. Used to enable incremental mirroring and avoid full blind syncs.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The second sentence is a fragment. Consider revising it for better clarity and flow.

Suggested change
Returns a list of incident IDs that were modified since the last sync. Used to enable incremental mirroring and avoid full blind syncs.
Returns a list of incident IDs that were modified since the last sync. This command is used to enable incremental mirroring and avoid full blind syncs.


| **Argument Name** | **Description** | **Required** |
| --- | --- | --- |
| lastUpdate | ISO8601 timestamp of the last time the integration was synced. Only incidents modified after this time are returned. | Required |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The argument name lastUpdate uses camelCase, whereas XSOAR command arguments typically follow snake_case (e.g., last_update). Please verify if this aligns with the integration's naming conventions. Note that changing this would also require updating the integration YAML file.


##### XSOAR Mirroring

- Added the **get-modified-remote-data** command to support incremental mirroring.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Command names should be styled with triple asterisks (bold-italics). Please change **get-modified-remote-data** to ***get-modified-remote-data***. See Entity Styling.

@content-bot
Copy link
Copy Markdown
Contributor

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
Copy link
Copy Markdown
Contributor

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: failed
Report ID: 3449c0f7d30d9416

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

⚠️ AI-generated triage. Validate before acting.

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

Labels

docs-approved release-notes-only Indicates that this pull request has ONLY release notes to review for documentation process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants