// Update CHANGELOG.md with a new entry under the correct section. Parses existing structure, adds entries under [Unreleased], and assesses semver impact. Triggers on: after resource changes, bug fixes, documentation updates, or any notable project change.
Fetch the latest CAF abbreviations page from Microsoft Learn and compare against resourceDefinition.json official.slug values. Reports drift where the provider's slug differs from the official CAF slug. Triggers on: weekly scheduled audit, manual sync check.
Discover new Azure resources by fetching the latest azurerm provider resource list from the Terraform Registry and comparing against resourceDefinition.json. Identifies unsupported resources. Triggers on: weekly scheduled discovery, manual audit.
Provide step-by-step guidance for contributors based on their contribution type. References CONTRIBUTING.md and project conventions. Triggers on: new contributor questions, 'how do I contribute', contribution guidance requests.
Run test coverage analysis (make test_coverage), parse coverage percentage, compare against the 95% threshold, and flag regressions. Triggers on: PR checks, post-build validation, release prep.
Ensure documentation files under docs/resources/ and docs/data-sources/ reflect current resource types with accurate examples. Triggers on: after adding/updating resources, documentation audit.
Run end-to-end tests (make test_e2e or make test_e2e_quick), parse results, and produce a structured summary. Use after build succeeds to validate real Terraform workflows. Triggers on: post-build validation, PR checks, release verification.
| name | changelog-update |
| description | Update CHANGELOG.md with a new entry under the correct section. Parses existing structure, adds entries under [Unreleased], and assesses semver impact. Triggers on: after resource changes, bug fixes, documentation updates, or any notable project change. |
head -80 CHANGELOG.md
Identify the ## [Unreleased] section and its subsections (### Added, ### Changed, ### Fixed, ### Removed, ### Deprecated).
| Change type | Section | Semver impact |
|---|---|---|
| New resource type added | ### Added | Minor |
| New feature or capability | ### Added | Minor |
| Updated resource constraints (slug, regex, length) | ### Changed | Patch |
| Bug fix | ### Fixed | Patch |
| Removed resource or feature | ### Removed | Major |
| Deprecated resource or feature | ### Deprecated | Minor |
Use these templates based on change type:
New resource:
- **RESOURCE**: Added `<resource_name>` (<official display name>) -- slug: `<slug>`, length: <min>-<max>, scope: <scope>, dashes <allowed|not allowed>, <lowercase|mixed case>
- Impact: <Low|Medium|High> -- <brief justification>
Updated resource:
- **RESOURCE**: Updated `<resource_name>` -- <describe field changes>
- Impact: <Low|Medium|High> -- <brief justification>
Bug fix:
- **<Component>**: <Brief description of fix>
- <Detail of what was fixed and why>
- Impact: <Low|Medium|High> -- <brief justification>
Multiple resources (batch):
- **RESOURCE**: Added support for <category> resource types
- Added `<resource_1>` with slug `<slug_1>`
- Added `<resource_2>` with slug `<slug_2>`
- <Summary of shared characteristics>
- Impact: <Low|Medium|High> -- <brief justification>
Insert the new entry under the appropriate subsection within ## [Unreleased].
### Added) does not exist, create it under ## [Unreleased].After inserting, summarize the semver impact: