digitalocean / digitalocean/doctl
doctl compute action list is SLOW
- Dominant language
- Go
- Stars
- 3.4k
- Forks
- 496
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 31
Description
**Describe the Issue:**
`doctl compute action list --after=2025-04-11T00:00:00.00Z` is VERY slow ~5 minutes. (Note: this is for <1 day of actions at time of posting)
**Environment:**
- doctl version: doctl version 1.124.0-release
- OS: MacOS Sequoia Version 15.4 (24E248)
- Installation method: Homebrew
**Additional Details:**
I can't post the `--trace` here, it's FAR too big. But, when I run it with `--trace` it shows that it's trying to recursively loop over every single paginated API request (Ex: `GET /v2/actions?page=126&per_page=200`). We have a LOT of actions; 52,292 according to the output. That means that it's making 262 asynchronous API requests. Even if I pass an `--action-type=power_off`, it still makes the same non-filtered request. I now realize I'm probably barking up the wrong tree _here_ because looking at the API docs, this seems to be an API limitation as there's no way to filter actions (except pagination).
Is there any _other_ way to find the date a droplet was powered off via the CLI?
(edit) It looks like there's no super reliable way even using the action list. There are a handful of servers that we have that are powered off that NEVER got the `power_off` action logged. Some were powered off to be re-sized years ago but were actually powered off the other day.
Contributor guide
Assessment
This issue has not been assessed yet.