Commit 095978c
committed
fix: read Link cursor from OktaAPIResponse in extract_after_cursor
The request-executor path (used by the resilient list_applications/list_group_apps
fetch) returns an OktaAPIResponse, which exposes headers via get_headers()/_resp_headers
and does not set _next. extract_after_cursor only looked for a .headers attribute, so
the Link cursor was never found and pagination stopped after the first page — listings
silently truncated to one page (e.g. 20 items) instead of paginating.
Resolve headers from .headers, get_headers(), or _resp_headers so the cursor is found
regardless of response shape. Adds tests for both executor-response shapes.
Refs #481 parent 83b44fc commit 095978c
2 files changed
Lines changed: 42 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
28 | | - | |
29 | | - | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
30 | 48 | | |
31 | 49 | | |
32 | | - | |
| 50 | + | |
33 | 51 | | |
34 | | - | |
| 52 | + | |
35 | 53 | | |
36 | | - | |
| 54 | + | |
37 | 55 | | |
38 | 56 | | |
39 | 57 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
106 | 106 | | |
107 | 107 | | |
108 | 108 | | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
| 118 | + | |
| 119 | + | |
| 120 | + | |
| 121 | + | |
| 122 | + | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
109 | 128 | | |
110 | 129 | | |
111 | 130 | | |
| |||
0 commit comments