Wez Furlong be2eeda1f5 the bounce API endpoint is now always asynchronous ...

In systems with very large numbers of queues, it will take an
effectively unbounded amount of time to produce the initial
summary of results if we were to wait for the bounce to be
applied to every queue.

Let's adjust the output of the kcli to indicate that it is async,
and update the docs which already suggested that the numbers would
be partial to indicate that you can only really consume the id
from the response.

2024-09-13 08:52:54 -07:00

..

_index.md

docs: split start_http_listener into multiple pages

2024-08-18 22:18:59 -07:00

api_admin_bounce_cancel_v1.md

add docs for new bounce APIs

2023-06-22 12:59:36 -07:00

api_admin_bounce_list_v1.md

add docs for new bounce APIs

2023-06-22 12:59:36 -07:00

api_admin_bounce_v1.md

the bounce API endpoint is now always asynchronous

2024-09-13 08:52:54 -07:00

api_admin_set_diagnostic_log_filter_v1.md

add docs for new bounce APIs

2023-06-22 12:59:36 -07:00

api_inject_v1.md

docs: fmt

2024-09-06 17:17:29 -07:00

metrics.json.md

rename delayed_count -> scheduled_count in metrics

2023-04-12 12:07:58 -07:00

metrics.md

update metrics sample

2024-08-21 22:00:37 +00:00