Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Increase default level of feedback/confirmation in destructive commands #1264

Closed
ranweiler opened this issue Sep 22, 2021 · 1 comment · Fixed by #1283
Closed

Increase default level of feedback/confirmation in destructive commands #1264

ranweiler opened this issue Sep 22, 2021 · 1 comment · Fixed by #1283
Assignees
Labels
enhancement New feature or request

Comments

@ranweiler
Copy link
Member

Some CLI commands invoke requests to endpoints that don't return rich descriptions of executed actions. As a result, the CLI can be confusingly quiet, even when significant or destructive actions have been carried out.

An example from a user:

  1. For the jobs that do not have associated containers, running onefuzz jobs containers delete <job-id> doesn't output anything. It would help to e.g. render a JSON object that makes it clear that nothing was done (intentionally and successfully).

  2. For the above command, the --dryrun flag does not indicate whether the containers have already been deleted. It could be useful if it did. This may require tracking more container metadata, or making additional queries.

@ranweiler ranweiler added the enhancement New feature or request label Sep 22, 2021
@ghost ghost added the Needs: triage label Sep 22, 2021
@stishkin stishkin self-assigned this Sep 23, 2021
@stishkin
Copy link
Contributor

Opened separate bug to track (2) of the bug: #1282

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants