getDeployStreamApplicationsWithHttpInfo method
Live application fleet updates as Server-Sent Events
Holds the connection open as text/event-stream and pushes one watch event per application change. It opens with an ADDED frame for every application currently present — the same projection the applications list serves, so a client renders a complete fleet from the stream alone — and then forwards ADDED, MODIFIED and DELETED as they happen, with a keep-alive every 25 seconds that is also how a vanished client is noticed and its watch torn down. Read-only and TENANT-SCOPED, fail-closed: a platform SuperAdmin streams the whole fleet, a validated org member streams only its own org's applications, anyone else gets 403 and no stream. No cluster client configured is 503. If the deployment is not granted the watch verb the stream degrades to keep-alives only — the initial state still renders, it simply stops updating — rather than failing the connection.
Note: This method returns the HTTP Response.
Implementation
Future<Response> getDeployStreamApplicationsWithHttpInfo() async {
// ignore: prefer_const_declarations
final path = r'/v1/deploy/stream/applications';
// ignore: prefer_final_locals
Object? postBody;
final queryParams = <QueryParam>[];
final headerParams = <String, String>{};
final formParams = <String, String>{};
const contentTypes = <String>[];
return apiClient.invokeAPI(
path,
'GET',
queryParams,
postBody,
headerParams,
formParams,
contentTypes.isEmpty ? null : contentTypes.first,
);
}