awesome-copilot/prompts/update-avm-modules-in-bicep.prompt.md
Daniel Scott-Raynsford d260c65769 Add prompts for .NET best practices, design pattern review, GitHub Copilot suggestions, and various update tasks
- Created a prompt for .NET/C# best practices to ensure code quality and adherence to standards.
- Added a design pattern review prompt for evaluating C#/.NET code implementations.
- Introduced prompts for suggesting relevant GitHub Copilot chatmodes and prompts based on repository context.
- Developed a prompt for updating Azure Verified Modules in Bicep files to the latest versions.
- Implemented a prompt for updating implementation plans with new requirements and features.
- Created a prompt for updating the llms.txt file to reflect changes in documentation or specifications.
- Added a prompt for updating markdown file indexes with files from specified folders.
- Developed a prompt for updating object-oriented component documentation according to best practices.
- Created a prompt for updating specification files to align with new requirements and ensure AI-readiness.
2025-07-07 12:51:24 +12:00

49 lines
1.6 KiB
Markdown

---
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']
---
# Update Azure Verified Modules in Bicep Files
Update Bicep file `${file}` to use latest Azure Verified Module (AVM) versions.
## 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
## 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 | [📖](link) |
| avm/res/storage/account | 0.3.0 | 0.3.0 | ✅ | Current | [📖](link) |
## 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