-
Notifications
You must be signed in to change notification settings - Fork 285
Add Path and Tool parameters to DeployTestResources #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this 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 PR refactors the Deploy-TestResources.ps1 script to support the new tools-based directory structure by replacing the single Area parameter with two mutually exclusive parameter sets: Path (for direct path specification) and Tool (for tool-based deployment with partial matching). The changes include enhanced error handling and backward compatibility considerations.
Key changes:
- Replaced single
Areaparameter withPathandToolparameter sets for flexible resource deployment - Added intelligent tool matching with partial name support and clear error messages
- Updated documentation to reflect the new parameter structure and usage patterns
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| eng/scripts/Deploy-TestResources.ps1 | Refactored parameter structure from single Area to Path/Tool parameter sets with enhanced tool discovery logic |
| CONTRIBUTING.md | Updated documentation to reflect new directory structure, parameter usage, and deployment examples |
3daa837 to
fadbfeb
Compare
weshaggard
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like this to support multiple tools but that can come as a follow-up. We need to get this in so folks can run any local tests.
0cabe2a to
9b536cb
Compare
|
/azp run mcp - pullrequest - live |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi @hallipr could we update the https://github.com/microsoft/mcp/blob/main/CONTRIBUTING.md to reflect I drafted this PR #326 but I am not sure it has been covered all cases |
What does this PR do?
Deploy-TestResources wasn't updated to support the new tools/ paths.
This changes the parameter from 'Area' to 'Tool' and 'Path'.
GitHub issue number?
fixes #38
Pre-merge Checklist
CHANGELOG.mdfor product changes (features, bug fixes, UI/UX, updated dependencies).\eng\common\spelling\Invoke-Cspell.ps1README.mddocumentation/docs/azmcp-commands.md/docs/e2eTestPrompts.mdToolDescriptionEvaluatorand obtained a score of0.4or more and a top 3 ranking for all related test promptscrypto mining, spam, data exfiltration, etc.)/azp run azure - mcpto run Live Test Pipeline