Tags: microsoft/GitHub-Copilot-for-Azure
Tags
Fix azure cost rate limiting (#1766) * Fix azure-cost 40% failure rate from Cost Management API rate limiting Update skill documentation to teach the agent proper 429 retry-after header handling across all three Cost Management rate-limit headers: - x-ms-ratelimit-microsoft.costmanagement-qpu-retry-after - x-ms-ratelimit-microsoft.costmanagement-entity-retry-after - x-ms-ratelimit-microsoft.costmanagement-tenant-retry-after The agent must check whichever headers are present, take the maximum retry-after value, and not retry until that duration has elapsed. Skill doc changes: - Add rate limit thresholds table to cost-query and cost-forecast guardrails - Add 'Handling 429 Responses' section with all-headers guidance - Fix 429 retry rows in error-handling.md to reference all 3 headers - Add per-scope rate limit warnings in workflow files - Add rate-limit best practice to SKILL.md, bump version to 1.1.0 Test changes: - Reduce RUNS_PER_PROMPT from 5 to 3 to lower rate limit pressure - Lower invocationRateThreshold from 0.8 to 0.6 (2/3 must pass) - Add new 429 response-quality test for rate limit handling Resolves AB#37441409 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix casing for request body of forecast and query * fix PR comments * add headers and upgrade invocation rate threshold * update casing in guardrails --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Fix: azure-validate bypassed for containerized Container Apps deploym… …ents (#1796) * Initial plan * Fix container apps validation bypass: strengthen azure-prepare handoff and add container-specific triggers to azure-validate - Add Container Apps/containerized keywords to azure-validate SKILL.md description - Change azure-prepare Phase 2 Step 7 from⚠️ to ⛔ MANDATORY with explicit no-azd-up warning - Strengthen azure-prepare Next section with ⛔ and explicit Container Apps coverage - Add Container Apps trigger tests to azure-validate/triggers.test.ts - Update snapshots for both skills - Bump azure-validate version 1.0.3 → 1.0.4 - Bump azure-prepare version 1.1.12 → 1.1.13 Agent-Logs-Url: https://github.com/microsoft/GitHub-Copilot-for-Azure/sessions/59762ee6-88b6-46bf-916f-fd793f66ba29 Co-authored-by: fanyang-mono <52458914+fanyang-mono@users.noreply.github.com> * Revise azure-validate skill documentation Updated the description and guidance for the azure-validate skill, including validation steps and prerequisites. * Fix snapshot --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: fanyang-mono <52458914+fanyang-mono@users.noreply.github.com> Co-authored-by: Fan Yang <yangfan@microsoft.com>
Add cleanup script for test resources (#1603) * add cleanup script for test resources * add readme * update formatting * update scripts * address script comments * update script * Update eng/scripts/Metadata-Helpers.ps1 Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * address comments * Update eng/README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update eng/scripts/Resource-Helpers.ps1 Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update eng/scripts/test-sub-cleanup.ps1 Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update eng/scripts/Resource-Helpers.ps1 Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update eng/scripts/test-sub-cleanup.ps1 Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: kvenkatrajan <102772054+kvenkatrajan@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
fix: Add Docker build context validation to azure-validate skill (#1586) * Add Docker build context validation to azure-validate skill Pre-validate Docker build context during azure-validate by checking for package-lock.json when npm ci is specified in a Dockerfile. This prevents Docker build failures during azd package/up that waste time and can push deployments past test timeouts. Changes: - AZD recipe: Add step 9 (Docker Build Context Validation) between Build Verification and Package Validation - AZCLI recipe: Enhance Docker Build step with build context pre-validation before attempting docker build - AZD/AZCLI errors: Add npm ci / package-lock.json missing error entry - Bump azure-validate version to 1.0.3 Fixes #1557 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update plugin/skills/azure-validate/references/recipes/azd/README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update plugin/skills/azure-validate/references/recipes/azd/README.md --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Add more Aspire instructions (#1549) * Add more Aspire instructions Fixes #1535. In #1535, the test proceeded with an attempted deployment even though the Aspire project has no deployable resources. Here we add some further instructions about what to do in this situation. * Update plugin/skills/azure-prepare/references/aspire.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
PreviousNext