feat(resources): implement virtual resource type base class for abstract/computed resources #8610

Open
opened 2026-04-13 21:15:11 +00:00 by HAL9000 · 0 comments
Owner

Metadata

  • Commit message type: feat
  • Scope: resources
  • Branch name prefix: feat/v3.6.0-virtual-resource-types

Background and Context

As part of Epic #8568 (Resource Types & Container Tool Execution), virtual resource types represent abstract or computed resources that don't map to physical files. Examples include: computed metrics, API endpoints, or derived data.

This issue blocks Epic #8568.

Expected Behavior

  • VirtualResource base class is defined with: name, description, compute_fn
  • Virtual resources can be computed on demand via compute_fn
  • Virtual resources can be referenced in plans and actors
  • Virtual resources are documented with examples

Acceptance Criteria

  • VirtualResource base class is defined with name, description, compute_fn
  • Virtual resources can be computed on demand
  • Virtual resources can be referenced in plans
  • At least 2 example virtual resource implementations are provided
  • Unit tests achieve >= 97% coverage

Subtasks

  • Design VirtualResource base class interface
  • Implement VirtualResource base class
  • Implement 2 example virtual resources (e.g., MetricResource, APIEndpointResource)
  • Write unit tests for virtual resource types

Definition of Done

  1. Virtual resource type base class is implemented
  2. Example implementations are provided
  3. Unit tests pass with >= 97% coverage
  4. Code reviewed and merged to main branch

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Metadata - **Commit message type**: `feat` - **Scope**: `resources` - **Branch name prefix**: `feat/v3.6.0-virtual-resource-types` ## Background and Context As part of Epic #8568 (Resource Types & Container Tool Execution), virtual resource types represent abstract or computed resources that don't map to physical files. Examples include: computed metrics, API endpoints, or derived data. This issue blocks Epic #8568. ## Expected Behavior - `VirtualResource` base class is defined with: name, description, compute_fn - Virtual resources can be computed on demand via `compute_fn` - Virtual resources can be referenced in plans and actors - Virtual resources are documented with examples ## Acceptance Criteria - [ ] `VirtualResource` base class is defined with name, description, compute_fn - [ ] Virtual resources can be computed on demand - [ ] Virtual resources can be referenced in plans - [ ] At least 2 example virtual resource implementations are provided - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Design `VirtualResource` base class interface - [ ] Implement `VirtualResource` base class - [ ] Implement 2 example virtual resources (e.g., `MetricResource`, `APIEndpointResource`) - [ ] Write unit tests for virtual resource types ## Definition of Done 1. Virtual resource type base class is implemented 2. Example implementations are provided 3. Unit tests pass with >= 97% coverage 4. Code reviewed and merged to main branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.6.0 milestone 2026-04-13 21:18:26 +00:00
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.

Dependencies

No dependencies set.

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