-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logs ls --number has no effect #936
Comments
This is fixed in #939 but still waiting on a release. |
@willvedd Why is the maximum only 1000? That greatly reduces the utility of this in my mind; i.e. it's still not really all that useful if it can only go back 1000 log entries. |
Arbitrarily set at 1000 for practically; there is no technical limitation. IMO, this will satisfy most (but obviously not all) use cases around logs. And we need to bound at some point. It would help to understand the workflow you're trying to achieve. Short of upping the limit a little, we're unlikely to immediately implement but it is still important for us to know the features you want for the CLI. |
I would also like to see a higher number, but primarily so that I can determine easily how many particular errors of a specific kind have occurred. If a utility for the CLI allowed you to do this, it would probably be okay to cap the total number returned at 1000. There doesn't seem to be a query to do this with the Lucene filters. For example, I was trying to use the |
@DannyPat44 Sorry for the late response, We started looking again into the issue.. |
Checklist
Description
Poked at the code, and there's simply no code that loops over pages:
https://github.com/auth0/auth0-cli/blob/main/internal/cli/logs.go#L172-L189
Expectation
Passing in -n/--number >100 should fetch more than 100 log entries.
Reproduction
auth0 logs ls --number 100000
Auth0 CLI version
❯ auth0 -v
auth0 version 1.3.0 2bd069c
The text was updated successfully, but these errors were encountered: