No (documented) changes yet.
Client#get_node_memory_footprintis a new function that returns a node memory footprint breakdown.responses::NodeMemoryFootprintandresponses::NodeMemoryBreakdownare the key types that provide access to per-category proportions, both absolute and relative (in percent)
-
New
responses::HealthCheckFailureDetailsvariants to accommodate active port and protocol listener health checks -
New health check function:
Client#health_check_protocol_listener
-
New functions for listing stream connections, publishers and consumers:
Client#list_stream_publishers,Client#list_stream_publishers_in,Client#list_stream_publishers_of,Client#list_stream_publishers_on_connection,Client#list_stream_consumers,Client#list_stream_consumers_in,Client#list_stream_consumers_on_connection,Client#list_stream_connections,Client#list_stream_connections_in -
New health check function:
Client#health_check_port_listener
Client#list_feature_flags,Client#enable_feature_flag,Client#enable_all_stable_feature_flagsare three new functions for working with feature flags
-
Client#list_all_deprecated_featuresandClient#list_deprecated_features_in_useare new functions for listing all deprecated features and only those whose use is detected in the cluster. -
Client#list_feature_flagsis a new function that lists all feature flags in the cluster, including their state and stability.
- Bumps minimum
reqwestversion to0.12.11
-
To propagate more request context to the caller,
crate::error::Errorwas updated to provide a requset URL, a header map, and a request body (if available).This reason for doing this comes down to how
reqwest'sResponsefunctions are designed: the ones that consume and parse the body also consumeself, which means propagating aResponseto the caller is not very useless at best, and arguably is misleading.