// 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.
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.
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.
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 | azure-resource-discovery |
| description | 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. |
Use Terraform MCP tools (get_provider_capabilities) to list all resources in the azurerm provider:
provider_name: azurerm
provider_namespace: hashicorp
provider_document_type: resources
Alternatively, query the Terraform Registry API:
curl -s "https://registry.terraform.io/v1/providers/hashicorp/azurerm" | python3 -c "
import json, sys
data = json.load(sys.stdin)
print(json.dumps(data, indent=2))
"
grep '"name":' resourceDefinition.json | sed 's/.*"name": "//;s/".*//' | sort > /tmp/ard-supported.txt
# Identify resources in azurerm but not in our provider
comm -23 /tmp/ard-azurerm.txt /tmp/ard-supported.txt > /tmp/ard-missing.txt
# Count
MISSING=$(wc -l < /tmp/ard-missing.txt)
SUPPORTED=$(wc -l < /tmp/ard-supported.txt)
Group missing resources by Azure service category:
## Azure Resource Discovery Report
### Summary
- azurerm provider resources: <total>
- Supported in CAF provider: <supported>
- Missing from CAF provider: <missing>
- Coverage: <percentage>%
### Missing Resources by Category
#### Compute (<count>)
- `azurerm_<resource>` — <description if available>
#### Storage (<count>)
- `azurerm_<resource>`
...
### Priority Recommendations
Resources that should be added first (commonly used, well-documented):
1. `azurerm_<resource>` — <reason>
2. ...
rm -f /tmp/ard-*.txt