Skip to content

feat: require --yes confirmation for destructive operations - #183

Merged
gujieye merged 1 commit into
mainfrom
feat/confirm-destructive-ops
Aug 31, 2026
Merged

feat: require --yes confirmation for destructive operations#183
gujieye merged 1 commit into
mainfrom
feat/confirm-destructive-ops

Conversation

@gujieye

@gujieye gujieye commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add a --yes + confirmDangerousAction high-risk confirmation guard to the destructive commands: finetune delete, deploy delete, dataset delete, and quota update --delete
  • In non-TTY environments, running without --yes now exits with USAGE(2) and points to --yes; the confirmation gate runs after --dry-run and before any network call (for deploy delete, after the status precheck)
  • quota update only triggers confirmation on the --delete path; regular --rpm/--tpm updates are unaffected
  • Add e2e coverage and regenerate the skill references

Test plan

  • e2e: --help shows --yes, and non-TTY runs without --yes exit with code 2 for all four commands
  • vp check passes (0 errors)
  • references regenerated via pnpm run sync:skill-assets are committed

- finetune/deploy/dataset delete: add --yes flag + confirmDangerousAction
- quota update --delete: confirm before clearing rate limits
- non-TTY runs without --yes fail with a USAGE error
- add e2e coverage and regenerate skill references
@gujieye
gujieye merged commit 3f78de2 into main Aug 31, 2026
2 checks passed
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.

1 participant