Add --update-endpoint option for messaging endpoint management

[joratz]

This pull request adds support for custom messaging endpoint registration and endpoint updates in the Agent365 CLI setup commands. The main changes introduce anew command-line options (--update-endpoint) for blueprint setup, allowing users to update an existing endpoint. The implementation ensures proper validation, logging, and configuration updates throughout the workflow.

New CLI options and endpoint management features:

• Added --update-endpoint option to the blueprint setup subcommand, allowing users to delete the existing messaging endpoint and register a new one with a specified URL. This includes a new helper method for endpoint update logic, validation, and configuration syncing. [1] [2]

Validation and configuration changes:

• Modified the endpoint registration helper to support custom endpoints, including proper naming conventions and logging for both Azure and non-Azure deployments.

Handler and workflow integration:

• Refactored command handlers to accept and process the new options, including dry-run logging, endpoint resolution, and integration into the setup workflow. [1] [2] [3] [4] [5] [6]
• Added helper methods for resolving custom endpoint values and for updating endpoints, with comprehensive logging and error handling. [1] [2]

These changes provide more flexibility for messaging endpoint management during agent blueprint setup, supporting advanced deployment scenarios and improving user experience.

Fixes #129 and #140

[Copilot]

Pull request overview

This pull request adds messaging endpoint management capabilities to the Agent365 CLI by introducing two new command-line options: --custom-endpoint for overriding endpoint URLs during registration, and --update-endpoint for replacing existing endpoints. The implementation provides comprehensive validation, error handling, and configuration syncing to support both Azure and non-Azure deployment scenarios.

Changes:

• Added --custom-endpoint option to all and blueprint setup subcommands for endpoint URL override during registration
• Added --update-endpoint option to blueprint subcommand for deleting and re-registering messaging endpoints
• Enhanced endpoint registration logic to support custom endpoint URLs with proper validation and naming conventions

Reviewed changes

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

Show a summary per file

File	Description
SetupCommandTests.cs	Added tests verifying the presence and behavior of the --custom-endpoint option in the all subcommand
BlueprintSubcommandTests.cs	Added comprehensive tests for both --custom-endpoint and --update-endpoint options, covering success cases, validation failures, and edge cases
SetupHelpers.cs	Modified RegisterBlueprintMessagingEndpointAsync to accept an optional custom endpoint parameter with HTTPS validation and endpoint naming logic
BlueprintSubcommand.cs	Added command options, handler logic, UpdateEndpointAsync method for endpoint updates, and ResolveCustomEndpoint helper method
AllSubcommand.cs	Added --custom-endpoint option and integrated it into the setup workflow with dry-run logging support

[Copilot]

Pull request overview

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

[tmlsousa]

Will this continue to support local endpoints like devtunnel and ngrok? Those used to be good for testing during development

[joratz]

Will this continue to support local endpoints like devtunnel and ngrok? Those used to be good for testing during development

Yes, there should be no change in supported endpoints as a result of this change.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.