box events missing pagination options and stream_position parameter
See original GitHub issueI’m trying to create an automatic events report system for my client but it turns out Boxcli can only return 500 items max and has no pagination option.
Here’s the use case, we would like to run a daily batch that runs at midnight and returns all logs from the prior day. Thecreated-after
query does not return more than 500 items. I would like to iterate thru the results until it returns 0 items.
box events -e --created-after=created-after
Also the result does not include the streamposition
value. It would be great if I could get that result as a --id-only
param and iterate thru results.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Stream Position Pagination - Box Developer Documentation
Guides Events Event Stream Parameters Stream Position Pagination ... First, send a request to the GET /events API without a stream_position query parameter....
Read more >Using AWS CLI pagination options
Use pagination options to optimize the output of AWS Command Line Interface (AWS CLI) API calls. ... How to use the --no-paginate parameter....
Read more >How to Build a Custom Pagination Component in React
Let's first look at what values we need as props to our Pagination component: totalCount: represents the total count of data available from...
Read more >Pagination - Bootstrap
Pagination · Overview. We use a large block of connected links for our pagination, making links hard to miss and easily scalable—all while...
Read more >REST Pagination in Spring - Baeldung
Pagination in a Spring REST Service - URI structure and best practice ... out-of-the-box methods that support using Pageable as a parameter.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@isaac-galvan Great! I’ll start work on this today and link this issue to the PR when it’s ready.
@mattwiller I think the second option, to provide a start and end time, would be best. This would fit our use case best, I believe.