Skip to content

resource update/delete are interactive-only (inquirer picker requires a real TTY) — blocks scripted/CI usage #79

Description

@GTCC777

Version: acp-cli 1.0.29

Repro:

  1. acp resource update (or acp resource delete) in any non-interactive context — CI, a script, or piped stdin.
  2. The inquirer-based picker either crashes without a TTY or hangs indefinitely when fed fake/piped input.

Contrast: resource create accepts explicit flags (--params '{}' etc.) and works non-interactively; update/delete have no equivalent flag path (no --resource-id selection), so the only scripted workaround is delete-and-recreate — and delete itself has the same TTY problem, so in practice resources can only be replaced by creating new ones.

Expected: update/delete accept an explicit --resource-id (mirroring --offering-id elsewhere in the CLI) so they can run headless.

Context: we run 4 seller agents 24/7 with scripted deploy/config management; every resource change currently requires a manual terminal session.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions