feat(resource): define Azure networking resource types (azure-vnet, azure-subnet, azure-nsg) #2426

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

Metadata

  • Branch: feat/v360/azure-networking-types
  • Commit Message: feat(resource): define azure-vnet, azure-subnet, and azure-nsg 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 networking resource types following the generic cloud-* base layer pattern established by PR #669.

Azure networking resources form a containment hierarchy: azure-subscriptionazure-resource-groupazure-vnetazure-subnet. Network security groups (azure-nsg) can be associated with subnets or NICs.

Expected Behavior

  • azure-vnet inherits from cloud-network, is auto-discovered as a child of azure-resource-group
  • azure-subnet inherits from cloud-subnet, is auto-discovered as a child of azure-vnet
  • azure-nsg inherits from cloud-security-group, is auto-discovered as a child of azure-resource-group
  • All types are non-user-addable
  • All types pass ResourceTypeSpec.from_config() validation
  • Inheritance chain depth ≤ 5 levels (ADR-042)

Acceptance Criteria

  • azure-vnet defined with inherits: cloud-network, parent azure-resource-group, user_addable: false
  • azure-subnet defined with inherits: cloud-subnet, parent azure-vnet, user_addable: false
  • azure-nsg defined with inherits: cloud-security-group, parent azure-resource-group, user_addable: false
  • All three types registered in the resource type registry
  • All three types pass ResourceTypeSpec.from_config() validation
  • Inheritance chain ≤ 5 levels deep for all types
  • All nox stages pass
  • Coverage ≥ 97%

Dependencies

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

Subtasks

  • Define azure-vnet resource type config with inherits: cloud-network, parent azure-resource-group
  • Define azure-subnet resource type config with inherits: cloud-subnet, parent azure-vnet
  • Define azure-nsg resource type config with inherits: cloud-security-group, parent azure-resource-group
  • Register all three types in the resource type registry
  • Validate all 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-vnet, azure-subnet, and azure-nsg 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-networking-types` - **Commit Message**: `feat(resource): define azure-vnet, azure-subnet, and azure-nsg 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 networking resource types following the generic `cloud-*` base layer pattern established by PR #669. Azure networking resources form a containment hierarchy: `azure-subscription` → `azure-resource-group` → `azure-vnet` → `azure-subnet`. Network security groups (`azure-nsg`) can be associated with subnets or NICs. ## Expected Behavior - `azure-vnet` inherits from `cloud-network`, is auto-discovered as a child of `azure-resource-group` - `azure-subnet` inherits from `cloud-subnet`, is auto-discovered as a child of `azure-vnet` - `azure-nsg` inherits from `cloud-security-group`, is auto-discovered as a child of `azure-resource-group` - All types are non-user-addable - All types pass `ResourceTypeSpec.from_config()` validation - Inheritance chain depth ≤ 5 levels (ADR-042) ## Acceptance Criteria - [ ] `azure-vnet` defined with `inherits: cloud-network`, parent `azure-resource-group`, `user_addable: false` - [ ] `azure-subnet` defined with `inherits: cloud-subnet`, parent `azure-vnet`, `user_addable: false` - [ ] `azure-nsg` defined with `inherits: cloud-security-group`, parent `azure-resource-group`, `user_addable: false` - [ ] All three types registered in the resource type registry - [ ] All three types pass `ResourceTypeSpec.from_config()` validation - [ ] Inheritance chain ≤ 5 levels deep for all types - [ ] All nox stages pass - [ ] Coverage ≥ 97% ## Dependencies - Blocked by: #2425 (azure-subscription and azure-resource-group must exist first) - Blocks: #1019 ## Subtasks - [ ] Define `azure-vnet` resource type config with `inherits: cloud-network`, parent `azure-resource-group` - [ ] Define `azure-subnet` resource type config with `inherits: cloud-subnet`, parent `azure-vnet` - [ ] Define `azure-nsg` resource type config with `inherits: cloud-security-group`, parent `azure-resource-group` - [ ] Register all three types in the resource type registry - [ ] Validate all 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-vnet`, `azure-subnet`, and `azure-nsg` 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#2426
No description provided.