feat(resource): define Azure compute resource types (azure-vm, azure-managed-disk) #2427

Open
opened 2026-04-03 18:01:40 +00:00 by freemo · 0 comments
Owner

Metadata

  • Branch: feat/v360/azure-compute-types
  • Commit Message: feat(resource): define azure-vm and azure-managed-disk resource types
  • Milestone: v3.6.0
  • Parent Epic: #1019

Background

Part of the Azure cloud resource hierarchy expansion (Epic #1019). This issue implements the Azure compute resource types following the generic cloud-* base layer pattern established by PR #669.

Azure compute resources are auto-discovered within a resource group and subnet: azure-resource-groupazure-vm. Managed disks are attached to VMs: azure-vmazure-managed-disk.

Expected Behavior

  • azure-vm inherits from cloud-compute-instance, is auto-discovered as a child of azure-resource-group (and optionally azure-subnet)
  • azure-managed-disk inherits from cloud-block-storage, is auto-discovered as a child of azure-vm
  • Both types are non-user-addable
  • Both types pass ResourceTypeSpec.from_config() validation
  • Inheritance chain depth ≤ 5 levels (ADR-042)

Acceptance Criteria

  • azure-vm defined with inherits: cloud-compute-instance, parent azure-resource-group, user_addable: false
  • azure-managed-disk defined with inherits: cloud-block-storage, parent azure-vm, user_addable: false
  • Both types registered in the resource type registry
  • Both types pass ResourceTypeSpec.from_config() validation
  • Inheritance chain ≤ 5 levels deep
  • All nox stages pass
  • Coverage ≥ 97%

Dependencies

  • Blocked by: #2425 (azure-subscription and azure-resource-group must exist first)
  • Blocks: #1019

Subtasks

  • Define azure-vm resource type config with inherits: cloud-compute-instance, parent azure-resource-group
  • Define azure-managed-disk resource type config with inherits: cloud-block-storage, parent azure-vm
  • Register both types in the resource type registry
  • Validate both types pass ResourceTypeSpec.from_config() validation
  • Run nox (all default sessions), fix any errors
  • Verify coverage ≥ 97% via nox -s coverage_report

Definition of Done

  • All subtasks completed and checked off
  • azure-vm and azure-managed-disk resource types are defined, registered, and validated
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done
  • All nox stages pass
  • Coverage ≥ 97%

Automated by CleverAgents Bot
Supervisor: Unknown | Agent: ca-epic-planner

## Metadata - **Branch**: `feat/v360/azure-compute-types` - **Commit Message**: `feat(resource): define azure-vm and azure-managed-disk resource types` - **Milestone**: v3.6.0 - **Parent Epic**: #1019 ## Background Part of the Azure cloud resource hierarchy expansion (Epic #1019). This issue implements the Azure compute resource types following the generic `cloud-*` base layer pattern established by PR #669. Azure compute resources are auto-discovered within a resource group and subnet: `azure-resource-group` → `azure-vm`. Managed disks are attached to VMs: `azure-vm` → `azure-managed-disk`. ## Expected Behavior - `azure-vm` inherits from `cloud-compute-instance`, is auto-discovered as a child of `azure-resource-group` (and optionally `azure-subnet`) - `azure-managed-disk` inherits from `cloud-block-storage`, is auto-discovered as a child of `azure-vm` - Both types are non-user-addable - Both types pass `ResourceTypeSpec.from_config()` validation - Inheritance chain depth ≤ 5 levels (ADR-042) ## Acceptance Criteria - [ ] `azure-vm` defined with `inherits: cloud-compute-instance`, parent `azure-resource-group`, `user_addable: false` - [ ] `azure-managed-disk` defined with `inherits: cloud-block-storage`, parent `azure-vm`, `user_addable: false` - [ ] Both types registered in the resource type registry - [ ] Both types pass `ResourceTypeSpec.from_config()` validation - [ ] Inheritance chain ≤ 5 levels deep - [ ] All nox stages pass - [ ] Coverage ≥ 97% ## Dependencies - Blocked by: #2425 (azure-subscription and azure-resource-group must exist first) - Blocks: #1019 ## Subtasks - [ ] Define `azure-vm` resource type config with `inherits: cloud-compute-instance`, parent `azure-resource-group` - [ ] Define `azure-managed-disk` resource type config with `inherits: cloud-block-storage`, parent `azure-vm` - [ ] Register both types in the resource type registry - [ ] Validate both types pass `ResourceTypeSpec.from_config()` validation - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage ≥ 97% via `nox -s coverage_report` ## Definition of Done - [ ] All subtasks completed and checked off - [ ] `azure-vm` and `azure-managed-disk` resource types are defined, registered, and validated - [ ] A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly - [ ] The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly - [ ] The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done - [ ] All nox stages pass - [ ] Coverage ≥ 97% --- **Automated by CleverAgents Bot** Supervisor: Unknown | Agent: ca-epic-planner
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#2427
No description provided.