-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
priority/highHigh priorityHigh prioritysolution/toolkitAzureLocal ToolkitAzureLocal Toolkittype/featureFeature requestFeature request
Description
Problem
Neither repo has been fully tested end-to-end for all IaC tools. We need a clear tracking matrix of each tool's maturity status across both repos. The AVD repo has not been tested at all and should reflect that status. The SOFS repo only has PowerShell fully tested.
Tool Maturity Matrix
azurelocal-avd
| Tool | Built | Tested | Released | Notes |
|---|---|---|---|---|
| Terraform | ✅ | ❌ | ❌ | Code exists, untested |
| Bicep | ✅ | ❌ | ❌ | Code exists, untested |
| ARM (JSON) | ✅ | ❌ | ❌ | Compiled from Bicep, untested |
| PowerShell | ✅ | ❌ | ❌ | Scripts exist, untested |
| Ansible | ✅ | ❌ | ❌ | Roles exist, untested |
| Azure CLI | ✅ | ❌ | ❌ | Scripts exist, untested |
azurelocal-sofs-fslogix
| Tool | Built | Tested | Released | Notes |
|---|---|---|---|---|
| Terraform | ✅ | ⏳ In Progress | ❌ | Azure resources complete, guest config delegates to Ansible |
| Bicep | ✅ | ⏳ In Progress | ❌ | Similar to Terraform |
| ARM (JSON) | ✅ | ❌ | ❌ | Compiled from Bicep, untested |
| PowerShell | ✅ | ✅ | ❌ | End-to-end tested |
| Ansible | ✅ | ❌ | ❌ | Playbooks exist, untested |
Actions Required
- Update AVD repo — Mark all tools as "untested" in docs/README (currently no status is shown, which implies it works)
- Update SOFS repo — Ensure tool status is accurately reflected
- Create a tracking mechanism — Either in this issue or a project board view that tracks Built → Tested → Released per tool per repo
- Define "Tested" — What constitutes tested? Manual end-to-end? Automated CI? Against real Azure Local?
- Define "Released" — What gates a tool from "Tested" to "Released"? (e.g., CI pipeline, docs complete, versioned)
- Prioritize testing order — Which tools matter most? (Terraform and PowerShell likely highest priority)
Acceptance Criteria
- Both repos have a visible maturity status table in their README or docs index
- AVD repo accurately reflects "untested" status for all tools
- SOFS repo maturity status is up to date
- Definition of "Built", "Tested", "Released" is documented
- Testing plan with prioritized order of tools to validate
- CI workflow to run basic validation (fmt/lint/build) even if not full e2e
Affected Repos
azurelocal-avd— README.md, docs/index.mdazurelocal-sofs-fslogix— README.md, docs/index.md
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
priority/highHigh priorityHigh prioritysolution/toolkitAzureLocal ToolkitAzureLocal Toolkittype/featureFeature requestFeature request