e1c7c7a50e
* Add prompts for .NET best practices, design pattern review, and GitHub Copilot suggestions - Introduced a comprehensive prompt for ensuring .NET/C# code adheres to best practices, covering documentation, design patterns, dependency injection, resource management, async patterns, testing standards, configuration, AI integration, error handling, performance, security, and code quality. - Added a prompt for reviewing C#/.NET code for design pattern implementation, providing a checklist for required patterns, architecture, best practices, SOLID principles, performance, maintainability, testability, security, documentation, code clarity, and clean code. - Created prompts for suggesting relevant GitHub Copilot chatmodes and prompts based on the current repository context, including a structured process for fetching available chatmodes/prompts, scanning local files, and presenting options with rationale. - Developed a prompt for updating Azure Verified Modules (AVM) in Bicep files, detailing the process for scanning, checking for updates, validating, and handling breaking changes. - Implemented a prompt for updating implementation plans with new requirements, ensuring machine-readable output and adherence to a strict template. - Added a prompt for updating the llms.txt file to reflect changes in documentation or specifications, focusing on compliance with the llmstxt specification. - Created a prompt for updating markdown file indices with files from specified folders, including options for table structures and update strategies. - Developed a prompt for updating object-oriented component documentation, following industry best practices and ensuring alignment with current implementations. - Added a prompt for updating specification files, emphasizing clarity, structure, and compliance with established documentation standards. * CHANGE: Update implementation plan prompt formatting - Renamed prompt title for clarity. - Added spacing for improved readability. - Enhanced structure to ensure compliance with template validation rules. * CHANGE: Fix typo in .NET best practices prompt - Corrected "soltion" to "solution" in the prompt description.
49 lines
1.6 KiB
Markdown
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
|