- Refactor input sections to use consistent headings. - Enhance clarity in documentation standards and requirements. - Update descriptions for better alignment with best practices. - Add comprehensive analysis and planning phases for LLMs. - Create new `llms.txt` file prompt for repository structure.
1.6 KiB
1.6 KiB
| mode | description | tools | |||||||
|---|---|---|---|---|---|---|---|---|---|
| agent | Update Azure Verified Modules (AVM) to latest versions in Bicep files. |
|
Update Azure Verified Modules in Bicep Files
Update Bicep file ${file} to use latest Azure Verified Module (AVM) versions.
Process
- Scan: Extract AVM modules and current versions from
${file} - Check: Fetch latest versions from MCR:
https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list - Compare: Parse semantic versions to identify updates
- Review: For breaking changes, fetch docs from:
https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource} - Update: Apply version updates and parameter changes
- Validate: Run
bicep lintto ensure compliance
Breaking Change Policy
⚠️ PAUSE for approval if updates involve:
- Incompatible parameter changes
- Security/compliance modifications
- Behavioral changes
Output Format
Display results in table with icons:
| Module | Current | Latest | Status | Action | Docs |
|---|---|---|---|---|---|
| avm/res/compute/vm | 0.1.0 | 0.2.0 | 🔄 | Updated | 📖 |
| avm/res/storage/account | 0.3.0 | 0.3.0 | ✅ | Current | 📖 |
Icons
- 🔄 Updated
- ✅ Current
- ⚠️ Manual review required
- ❌ Failed
- 📖 Documentation
Requirements
- Use MCR tags API only for version discovery
- Parse JSON tags array and sort by semantic versioning
- Maintain Bicep file validity and linting compliance