josiadmin/awesome-copilot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CHANGE: Update process and tools for AVM modules (#211)

Browse Source 
- Refined the process for updating Azure Verified Modules in Bicep files.
- Added steps for identifying unique AVM modules and validating updates.
- Updated tool usage guidelines to include additional tools.
- Clarified output format and summary requirements.
This commit is contained in:
Daniel Scott-Raynsford 2025-08-25 19:16:56 -07:00 committed by GitHub
parent b26d6e01e2
commit 3edd17eea0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 20 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
prompts/update-avm-modules-in-bicep.prompt.md
View File

@ -1,20 +1,26 @@
---
mode: 'agent'
description: 'Update Azure Verified Modules (AVM) to latest versions in Bicep files.'
tools: ['changes', 'codebase', 'editFiles', 'fetch', 'runCommands', 'azure_get_deployment_best_practices', 'azure_get_schema_for_Bicep']
tools: ['codebase', 'think', 'changes', 'fetch', 'searchResults', 'todos', 'editFiles', 'search', 'runCommands', 'bicepschema', 'azure_get_schema_for_Bicep']
---
# Update Azure Verified Modules in Bicep Files
Update Bicep file `${file}` to use latest Azure Verified Module (AVM) versions.
Update Bicep file `${file}` to use latest Azure Verified Module (AVM) versions. Limit progress updates to non-breaking changes. Don't output information other than the final outout table and summary.
## Process
1. **Scan**: Extract AVM modules and current versions from `${file}`
2. **Check**: Fetch latest versions from MCR: `https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list`
3. **Compare**: Parse semantic versions to identify updates
4. **Review**: For breaking changes, fetch docs from: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}`
5. **Update**: Apply version updates and parameter changes
6. **Validate**: Run `bicep lint` to ensure compliance
1. **Identify**: List all unique AVM modules used by matching `avm/res/{service}/{resource}` using `#search` tool
1. **Check**: Use `#fetch` tool to get latest version of each AVM module from MCR: `https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list`
1. **Compare**: Parse semantic versions to identify AVM modules needing update
1. **Review**: For breaking changes, use `#fetch` tool to get docs from: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}`
1. **Update**: Apply version updates and parameter changes using `#editFiles` tool
1. **Validate**: Run `bicep lint` and `bicep build` using `#runCommands` tool to ensure compliance.
1. **Output**: Summarize changes in a table format with summary of updates below.
## Tool Usage
Always use tools `#search`, `#searchResults`,`#fetch`, `#editFiles`, `#runCommands`, `#todos` if available. Avoid writing code to perform tasks.
## Breaking Change Policy
@ -26,13 +32,19 @@ Update Bicep file `${file}` to use latest Azure Verified Module (AVM) versions.
## Output Format
Display results in table with icons:
Only display results in table with icons:
```markdown
| Module | Current | Latest | Status | Action | Docs |
|--------|---------|--------|--------|--------|------|
| avm/res/compute/vm | 0.1.0 | 0.2.0 | 🔄 | Updated | [📖](link) |
| avm/res/storage/account | 0.3.0 | 0.3.0 | ✅ | Current | [📖](link) |
### Summary of Updates
Describe updates made, any manual reviews needed or issues encountered.
```
## Icons
- 🔄 Updated