feat: add chunk size argument to delete cli command #10813
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
argo list
CLI command accepts an--chunk-size n
argument, but theargo delete
command does not. In our case, this was problematic because the large number of old workflows we had was causing unbounded list queries to fail, and the sensible remedy (deleting old workflows) was not possible because (for example)argo delete --since 30d
could not be chunked in the same way that listing could.This PR adds a
--query-chunk-size n
argument toargo delete
, which is applied when the command is fetching the workflows it will delete. The namequery-chunk-size
is different from the list command optionchunk-size
to avoid the implication that it will delete according to the specified chunk - but please suggest a better name if you have one.The flag is passed directly to
listWorkflows
so follows the same code path as thelist
command.