cleveragents/cleveragents-core

Fork 3

UAT: `devcontainer-instance` missing `--config-path` and `--workspace-folder` CLI arguments specified in ADR-043 #3540

New issue

Open

opened 2026-04-05 19:06:33 +00:00 by freemo · 2 comments

freemo commented

2026-04-05 19:06:33 +00:00

Owner

Metadata

Branch: fix/devcontainer-instance-cli-args-config-path-workspace-folder
Commit Message: fix(resources): add --config-path and --workspace-folder CLI args to devcontainer-instance per ADR-043
Milestone: None (backlog)
Parent Epic: #398

Background

ADR-043 (§devcontainer-instance Resource Type) specifies that devcontainer-instance should support two additional CLI arguments beyond those inherited from container-instance:

CLI arguments: (inherited from container-instance) + --config-path (path to .devcontainer/devcontainer.json or .devcontainer/ directory, optional), --workspace-folder (host folder to mount as workspace, optional)

The current implementation in src/cleveragents/application/services/_resource_registry_data.py (lines 213–222) only defines a single --path argument for devcontainer-instance, and the agents resource add CLI command in src/cleveragents/cli/commands/resource.py exposes no --config-path or --workspace-folder options.

Expected behavior (from ADR-043):

agents resource add devcontainer-instance local/my-dc \
  --config-path /home/user/projects/web-app/.devcontainer/devcontainer.json \
  --workspace-folder /home/user/projects/web-app

Both --config-path and --workspace-folder should be optional CLI arguments for devcontainer-instance.

Actual behavior:
Only --path is available. There is no --config-path or --workspace-folder option.

Code locations:

src/cleveragents/application/services/_resource_registry_data.py lines 213–222: devcontainer-instance cli_args definition
src/cleveragents/cli/commands/resource.py lines 540–605: resource_add command — no --config-path or --workspace-folder options

Impact:
Users cannot specify a custom devcontainer.json path (e.g., for named configurations in .devcontainer/<name>/devcontainer.json) or explicitly set the workspace folder when registering a devcontainer-instance resource.

Backlog note: This issue was discovered during autonomous operation
on milestone v3.6.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Subtasks

Update devcontainer-instance entry in _resource_registry_data.py to replace the single --path arg with --config-path (optional, type path) and --workspace-folder (optional, type path) per ADR-043
Update resource_add CLI command in src/cleveragents/cli/commands/resource.py to accept and pass through --config-path and --workspace-folder options for devcontainer-instance
Ensure both arguments are optional and that validation logic handles the case where neither is provided
Write BDD unit test scenarios (Behave/Gherkin) in features/ covering: both args provided, only --config-path provided, only --workspace-folder provided, neither provided
Update integration tests in robot/ to exercise the new CLI arguments against a real devcontainer setup
Verify all nox sessions pass (nox -e lint, nox -e typecheck, nox -e unit_tests, nox -e integration_tests, nox -e coverage_report)

Definition of Done

devcontainer-instance cli_args in _resource_registry_data.py defines --config-path and --workspace-folder as optional path arguments matching ADR-043
resource_add CLI command accepts --config-path and --workspace-folder for devcontainer-instance resource type
BDD unit test scenarios written and passing for all argument combinations
Integration tests updated and passing
All nox stages pass
Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-new-issue-creator

## Metadata - **Branch**: `fix/devcontainer-instance-cli-args-config-path-workspace-folder` - **Commit Message**: `fix(resources): add --config-path and --workspace-folder CLI args to devcontainer-instance per ADR-043` - **Milestone**: None (backlog) - **Parent Epic**: #398 ## Background ADR-043 (§`devcontainer-instance` Resource Type) specifies that `devcontainer-instance` should support two additional CLI arguments beyond those inherited from `container-instance`: > **CLI arguments**: (inherited from `container-instance`) + `--config-path` (path to `.devcontainer/devcontainer.json` or `.devcontainer/` directory, optional), `--workspace-folder` (host folder to mount as workspace, optional) The current implementation in `src/cleveragents/application/services/_resource_registry_data.py` (lines 213–222) only defines a single `--path` argument for `devcontainer-instance`, and the `agents resource add` CLI command in `src/cleveragents/cli/commands/resource.py` exposes no `--config-path` or `--workspace-folder` options. **Expected behavior (from ADR-043):** ```bash agents resource add devcontainer-instance local/my-dc \ --config-path /home/user/projects/web-app/.devcontainer/devcontainer.json \ --workspace-folder /home/user/projects/web-app ``` Both `--config-path` and `--workspace-folder` should be optional CLI arguments for `devcontainer-instance`. **Actual behavior:** Only `--path` is available. There is no `--config-path` or `--workspace-folder` option. **Code locations:** - `src/cleveragents/application/services/_resource_registry_data.py` lines 213–222: `devcontainer-instance` `cli_args` definition - `src/cleveragents/cli/commands/resource.py` lines 540–605: `resource_add` command — no `--config-path` or `--workspace-folder` options **Impact:** Users cannot specify a custom devcontainer.json path (e.g., for named configurations in `.devcontainer/<name>/devcontainer.json`) or explicitly set the workspace folder when registering a `devcontainer-instance` resource. > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.6.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. ## Subtasks - [ ] Update `devcontainer-instance` entry in `_resource_registry_data.py` to replace the single `--path` arg with `--config-path` (optional, type `path`) and `--workspace-folder` (optional, type `path`) per ADR-043 - [ ] Update `resource_add` CLI command in `src/cleveragents/cli/commands/resource.py` to accept and pass through `--config-path` and `--workspace-folder` options for `devcontainer-instance` - [ ] Ensure both arguments are optional and that validation logic handles the case where neither is provided - [ ] Write BDD unit test scenarios (Behave/Gherkin) in `features/` covering: both args provided, only `--config-path` provided, only `--workspace-folder` provided, neither provided - [ ] Update integration tests in `robot/` to exercise the new CLI arguments against a real devcontainer setup - [ ] Verify all nox sessions pass (`nox -e lint`, `nox -e typecheck`, `nox -e unit_tests`, `nox -e integration_tests`, `nox -e coverage_report`) ## Definition of Done - [ ] `devcontainer-instance` `cli_args` in `_resource_registry_data.py` defines `--config-path` and `--workspace-folder` as optional path arguments matching ADR-043 - [ ] `resource_add` CLI command accepts `--config-path` and `--workspace-folder` for `devcontainer-instance` resource type - [ ] BDD unit test scenarios written and passing for all argument combinations - [ ] Integration tests updated and passing - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-new-issue-creator

freemo added a new dependency

2026-04-05 19:06:39 +00:00

#398 Epic: Post-MVP Resources

freemo referenced this issue

2026-04-05 19:13:23 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377

freemo commented

2026-04-05 19:35:40 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Low — The missing CLI arguments are a UX gap for advanced devcontainer configurations (named configurations, custom workspace folders). Basic devcontainer registration works with the existing --path argument.
Milestone: v3.6.0 — Devcontainer resource types are in scope for M7.
Story Points: 3 — M — Requires updating the registry data definition, modifying the CLI command to accept new options, validation logic, and tests. Moderate scope.
MoSCoW: Could Have — ADR-043 specifies these as optional arguments. The existing --path argument covers the common case. These are nice-to-have for advanced configurations.
Parent Epic: #398 (Post-MVP Resources)

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Low — The missing CLI arguments are a UX gap for advanced devcontainer configurations (named configurations, custom workspace folders). Basic devcontainer registration works with the existing `--path` argument. - **Milestone**: v3.6.0 — Devcontainer resource types are in scope for M7. - **Story Points**: 3 — M — Requires updating the registry data definition, modifying the CLI command to accept new options, validation logic, and tests. Moderate scope. - **MoSCoW**: Could Have — ADR-043 specifies these as optional arguments. The existing `--path` argument covers the common case. These are nice-to-have for advanced configurations. - **Parent Epic**: #398 (Post-MVP Resources) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo added this to the v3.6.0 milestone

2026-04-05 19:36:01 +00:00

freemo referenced this issue

2026-04-05 19:36:17 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377

freemo referenced this issue

2026-04-05 19:38:18 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377

freemo referenced this issue

2026-04-05 19:45:38 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377

freemo commented

2026-04-06 18:59:05 +00:00

Author

Owner

Milestone Triage Decision: Moved to Backlog

This devcontainer feature has been moved out of v3.6.0 during aggressive milestone triage. Devcontainer CLI arguments are infrastructure enhancements, not advanced concepts.

Reasoning:

v3.6.0 focus: Advanced concepts that extend beyond core MVP
This issue: Devcontainer-instance CLI args - infrastructure feature
Impact: Development tooling enhancement, not advanced conceptual capability

Should be addressed when devcontainer functionality is prioritized or in a dedicated development tooling milestone.

**Milestone Triage Decision: Moved to Backlog** This devcontainer feature has been moved out of v3.6.0 during aggressive milestone triage. Devcontainer CLI arguments are infrastructure enhancements, not advanced concepts. **Reasoning:** - v3.6.0 focus: Advanced concepts that extend beyond core MVP - This issue: Devcontainer-instance CLI args - infrastructure feature - Impact: Development tooling enhancement, not advanced conceptual capability Should be addressed when devcontainer functionality is prioritized or in a dedicated development tooling milestone.

freemo removed this from the v3.6.0 milestone

2026-04-06 23:39:01 +00:00