Hi,
Barbican pagination logic doesn't preserve URL filters, below is an example :
$ curl -s 'https://keymanager-XXX/v1/secrets?acl_only=false&secret_type=passphrase' -H "X-Auth-Token: ${OS_AUTH_TOKEN}" | jq -r | grep next "next": "https://keymanager-XXX:443/v1/secrets?limit=10&offset=10",
The "next" URL, generated by barbican API doesn't preserve the initial filter.
Here is glance API behavior just for comparison:
$ curl -s 'https://image-3.XXX/v2/images?limit=1&visibility=shared' -H "X-Auth-Token: ${OS_AUTH_TOKEN}" | jq -r | grep next "next": "/v2/images?limit=1&visibility=shared&marker=d000ba9a-7067-498c-ac8e-cb74fcf6e1b0"
Please let me know if further information is required
Regards, Rajiv
Hi,
Barbican pagination logic doesn't preserve URL filters, below is an example :
$ curl -s 'https:/ /keymanager- XXX/v1/ secrets? acl_only= false&secret_ type=passphrase ' -H "X-Auth-Token: ${OS_AUTH_TOKEN}" | jq -r | grep next /keymanager- XXX:443/ v1/secrets? limit=10& offset= 10",
"next": "https:/
The "next" URL, generated by barbican API doesn't preserve the initial filter.
Here is glance API behavior just for comparison:
$ curl -s 'https:/ /image- 3.XXX/v2/ images? limit=1& visibility= shared' -H "X-Auth-Token: ${OS_AUTH_TOKEN}" | jq -r | grep next limit=1& visibility= shared& marker= d000ba9a- 7067-498c- ac8e-cb74fcf6e1 b0"
"next": "/v2/images?
Please let me know if further information is required
Regards,
Rajiv