feat(devcontainer): Implement devcontainer-instance child resource types (container-mount, container-exec-env, container-port) #8978

Open
opened 2026-04-14 04:34:49 +00:00 by HAL9000 · 1 comment
Owner

Background and Context

Per ADR-043 and Epic #4952, the devcontainer-instance resource type must support three child resource types: container-mount (filesystem mounts), container-exec-env (execution environment variables), and container-port (port forwarding). Additionally, the container-instance resource type must support a --clone-into CLI argument for cloning repositories into containers.

Currently, devcontainer-instance does not model these child types, limiting the agent's ability to configure and manage devcontainer environments programmatically.

Parent Epic: #4952 (EPIC: Devcontainer Lifecycle Management — State Persistence & Auto-Discovery)

Acceptance Criteria

  • container-mount child resource type is implemented with source, target, and type fields
  • container-exec-env child resource type is implemented with key and value fields
  • container-port child resource type is implemented with host_port, container_port, and protocol fields
  • devcontainer-instance resource schema accepts and validates all three child types
  • container-instance resource type supports --clone-into <repo-url> CLI argument
  • All nox stages pass with coverage >= 97%

Subtasks

  • Define ContainerMountResource schema with source, target, type (bind/volume/tmpfs) fields
  • Define ContainerExecEnvResource schema with key, value fields
  • Define ContainerPortResource schema with host_port, container_port, protocol fields
  • Update DevcontainerInstanceResource to accept children of the three new types
  • Implement --clone-into CLI argument on container-instance resource commands
  • Wire child resource creation/deletion to the devcontainer lifecycle manager
  • Write unit tests for each new resource type schema
  • Write integration tests for child resource management
  • Run nox (all default sessions), fix any errors

Definition of Done

  • All acceptance criteria met
  • Tests written and passing (coverage >= 97%)
  • Code reviewed and approved
  • Documentation updated if needed
  • No regressions introduced

Metadata

  • Commit message: feat(devcontainer): add container-mount, container-exec-env, container-port child types
  • Branch name: feat/m6/devcontainer-child-types

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

## Background and Context Per ADR-043 and Epic #4952, the `devcontainer-instance` resource type must support three child resource types: `container-mount` (filesystem mounts), `container-exec-env` (execution environment variables), and `container-port` (port forwarding). Additionally, the `container-instance` resource type must support a `--clone-into` CLI argument for cloning repositories into containers. Currently, `devcontainer-instance` does not model these child types, limiting the agent's ability to configure and manage devcontainer environments programmatically. Parent Epic: #4952 (EPIC: Devcontainer Lifecycle Management — State Persistence & Auto-Discovery) ## Acceptance Criteria - [ ] `container-mount` child resource type is implemented with `source`, `target`, and `type` fields - [ ] `container-exec-env` child resource type is implemented with `key` and `value` fields - [ ] `container-port` child resource type is implemented with `host_port`, `container_port`, and `protocol` fields - [ ] `devcontainer-instance` resource schema accepts and validates all three child types - [ ] `container-instance` resource type supports `--clone-into <repo-url>` CLI argument - [ ] All nox stages pass with coverage >= 97% ## Subtasks - [ ] Define `ContainerMountResource` schema with `source`, `target`, `type` (bind/volume/tmpfs) fields - [ ] Define `ContainerExecEnvResource` schema with `key`, `value` fields - [ ] Define `ContainerPortResource` schema with `host_port`, `container_port`, `protocol` fields - [ ] Update `DevcontainerInstanceResource` to accept children of the three new types - [ ] Implement `--clone-into` CLI argument on `container-instance` resource commands - [ ] Wire child resource creation/deletion to the devcontainer lifecycle manager - [ ] Write unit tests for each new resource type schema - [ ] Write integration tests for child resource management - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done - [ ] All acceptance criteria met - [ ] Tests written and passing (coverage >= 97%) - [ ] Code reviewed and approved - [ ] Documentation updated if needed - [ ] No regressions introduced ## Metadata - **Commit message:** `feat(devcontainer): add container-mount, container-exec-env, container-port child types` - **Branch name:** `feat/m6/devcontainer-child-types` --- **Automated by CleverAgents Bot** Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.5.0 milestone 2026-04-14 04:44:57 +00:00
Author
Owner

Verified — Devcontainer child resource types are a v3.5.0 deliverable. MoSCoW: Must-have. Priority: Medium.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

✅ **Verified** — Devcontainer child resource types are a v3.5.0 deliverable. MoSCoW: Must-have. Priority: Medium. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
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#8978
No description provided.