Skip to content

Conversation

@ankushbindlish2
Copy link
Member

What does this PR do?

[Provide a clear, concise description of the changes]

[Any additional context, screenshots, or information that helps reviewers]

GitHub issue number?

[Link to the GitHub issue this PR addresses]

Pre-merge Checklist

  • Required for All PRs
    • Read contribution guidelines
    • PR title clearly describes the change
    • Commit history is clean with descriptive messages (cleanup guide)
    • Added comprehensive tests for new/modified functionality
    • Updated servers/Azure.Mcp.Server/CHANGELOG.md and/or servers/Fabric.Mcp.Server/CHANGELOG.md for product changes (features, bug fixes, UI/UX, updated dependencies)
  • For MCP tool changes:
    • One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
    • Updated servers/Azure.Mcp.Server/README.md and/or servers/Fabric.Mcp.Server/README.md documentation
    • Validate README.md changes using script at eng/scripts/Process-PackageReadMe.ps1. See Package README
    • Updated command list in /servers/Azure.Mcp.Server/docs/azmcp-commands.md and/or /docs/fabric-commands.md
    • Run .\eng\scripts\Update-AzCommandsMetadata.ps1 to update tool metadata in azmcp-commands.md (required for CI)
    • For new or modified tool descriptions, ran ToolDescriptionEvaluator and obtained a score of 0.4 or more and a top 3 ranking for all related test prompts
    • For tools with new names, including new tools or renamed tools, update consolidated-tools.json
    • For new tools associated with Azure services or publicly available tools/APIs/products, add URL to documentation in the PR description
  • Extra steps for Azure MCP Server tool changes:
    • Updated test prompts in /servers/Azure.Mcp.Server/docs/e2eTestPrompts.md
    • 👉 For Community (non-Microsoft team member) PRs:
      • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
      • Manual tests run: added comment /azp run mcp - pullrequest - live to run Live Test Pipeline

Added required directory-path, optional change-detection-mode, and paths options to the cloud endpoint change detection command. Updated service and option definitions to support these parameters, and adjusted tests and documentation accordingly for improved flexibility and control.
Refactored StorageSyncService to set ChangeDetectionMode using the constructor instead of Enum.TryParse. Updated live test to use 'Recursive' mode and an empty paths array. Updated assets.json tag for live tests.
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This pull request enhances the StorageSync cloud endpoint change detection command by adding optional parameters to provide more granular control over the change detection process. The changes replace the previous boolean recursive flag with a more flexible changeDetectionMode parameter and add support for specifying specific paths.

Key Changes:

  • Replaces the recursive boolean parameter with a changeDetectionMode string parameter that accepts values like "Default" or "Recursive"
  • Changes directoryPath from optional to required parameter
  • Adds a new paths parameter to allow specifying an array of specific paths for change detection
  • Updates tests, documentation, and command-line options to reflect the new parameter structure

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 6 comments.

Show a summary per file
File Description
tools/Azure.Mcp.Tools.StorageSync/src/Services/IStorageSyncService.cs Updates method signature to replace recursive boolean and optional filePaths with required directoryPath and optional changeDetectionMode and paths parameters
tools/Azure.Mcp.Tools.StorageSync/src/Services/StorageSyncService.cs Implements the new parameter handling logic, including conditional setting of change detection mode and path addition
tools/Azure.Mcp.Tools.StorageSync/src/Options/StorageSyncOptionDefinitions.cs Replaces Recursive option with ChangeDetectionMode and Paths options with updated descriptions
tools/Azure.Mcp.Tools.StorageSync/src/Options/CloudEndpoint/CloudEndpointTriggerChangeDetectionOptions.cs Adds properties for the new parameters: DirectoryPath, ChangeDetectionMode, and Paths
tools/Azure.Mcp.Tools.StorageSync/src/Commands/CloudEndpoint/CloudEndpointTriggerChangeDetectionCommand.cs Updates command registration and option binding to use the new parameters, makes DirectoryPath required
tools/Azure.Mcp.Tools.StorageSync/tests/Azure.Mcp.Tools.StorageSync.LiveTests/StorageSyncCommandTests.cs Updates test to include the new required parameters with sample values
tools/Azure.Mcp.Tools.StorageSync/tests/Azure.Mcp.Tools.StorageSync.LiveTests/assets.json Updates the tag for recorded test assets
servers/Azure.Mcp.Server/docs/azmcp-commands.md Updates command documentation to show the new required and optional parameters
servers/Azure.Mcp.Server/docs/e2eTestPrompts.md Updates the test prompt to include directory path parameter

@g2vinay g2vinay moved this from Untriaged to In Progress in Azure MCP Server Jan 10, 2026
@g2vinay g2vinay added this to the 2026-02 milestone Jan 10, 2026
Renamed the 'triggerchangedetection' command and related references to 'changedetection' for consistency and clarity across the StorageSync tool, documentation, and tests. Updated option descriptions for improved clarity.
@ankushbindlish2 ankushbindlish2 changed the title Microsoft.StorageSync | Adding optional arguments to trigger change detection command Microsoft.StorageSync | Adding arguments to trigger change detection command Jan 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

4 participants