Skip to content

fix(resource): support headless update and delete - #105

Open
hamadalmunyif wants to merge 3 commits into
Virtual-Protocol:mainfrom
hamadalmunyif:fix/resource-headless-lifecycle
Open

hamadalmunyif wants to merge 3 commits into
Virtual-Protocol:mainfrom
hamadalmunyif:fix/resource-headless-lifecycle

Conversation

@hamadalmunyif

@hamadalmunyif hamadalmunyif commented Oct 6, 2026 •

Copy link
Copy Markdown

Why

acp resource create already supports explicit flags, but resource update and resource delete still require interactive selection. This blocks scripted, CI, and other headless resource lifecycle management.

Fixes #79.

What

  • Add --resource-id to resource update and resource delete.
  • Add non-interactive update flags for name, description, URL, params, and hidden state.
  • Add --force to delete so scripted deletion does not prompt.
  • Preserve the existing interactive behavior when no resource ID is supplied.
  • Keep update semantics partial: omitted fields are left unchanged.
  • Document the new headless paths in README.md and SKILL.md.

The implementation follows the existing non-interactive patterns used by offering and subscription management and adds no dependencies.

Validation

Validated on the fork with Node 22:

  • npm install --ignore-scripts
  • npm run typecheck
  • npm run build

All three completed successfully.

Note: a fresh npm ci on the unmodified upstream baseline currently reports the lockfile as out of sync (utf-8-validate@5.0.10 missing). This PR does not modify dependencies or the lockfile.


Note

Low Risk
CLI-only changes to resource lifecycle commands with preserved interactive defaults; no auth, payment, or API contract changes.

Overview
Adds non-interactive paths for acp resource update and acp resource delete, matching offerings and subscriptions so CI and scripts can manage resources without prompts.

Update: --resource-id selects the resource; optional --name, --description, --url, --params, and --hidden / --no-hidden apply partial changes (omitted fields stay unchanged). With --resource-id, updates come only from flags—no readline prompts.

Delete: --resource-id targets a resource; --force skips the confirmation prompt.

Interactive behavior is unchanged when --resource-id is omitted. README.md and SKILL.md document the new flag-based examples.

Reviewed by Cursor Bugbot for commit 5526b60. Bugbot is set up for automated code reviews on this repo. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

1 participant