- Both
Amqp091ShovelSourceParamsandAmqp091ShovelDestinationParamsnow support a new boolean option,predeclared, that enables either or both sides to rely on a pre-declared topology
RuntimeParameterDefinition#name,RuntimeParameterDefinition#vhost, andRuntimeParameterDefinition#componenttypes changed fromStringto&str
-
Client#declare_amqp091_shovelis a new function that declares a dynamic shovel where both source and destination use AMQP 0-9-1 -
Client#delete_shovelis a new function for deleting shovels
-
Client#import_vhost_definitionsis a new function that imports virtual host-specific definition files (as opposed to cluster-wide ones) into the target virtual host -
Client#import_cluster_wide_definitionsis an alias toClient#import_definitionsto better reflect what it does
-
responses::VirtualHostDefinitionSetis an equivalent ofresponses::ClusterDefinitionSetbut adapted for the specific of virtual host-specific definitions, namely the fact that they do not contain virtual hosts, users, or permissions, and objects such as queues or bindings do not have the virtual host field to make it possible to import them into a virtual host with any name -
Client#export_vhost_definitions,Client#export_vhost_definitions_as_stringandClient#export_vhost_definitions_as_dataare new functions that export virtual host-specific definitions (as opposed to cluster-wide ones)
-
responses::DefinitionSetwas renamed toresponses::ClusterDefinitionSetto differentiate it from virtual host-specific definitions, which are from now on represented byresponses::VirtualHostDefinitionSet -
Client#export_definitionswas renamed toClient#export_cluster_wide_definitions -
Client#export_definitions_as_stringwas renamed toClient#export_cluster_wide_definitions_as_string -
Client#export_definitions_as_datawas renamed toClient#export_cluster_wide_definitions_as_data
Client#.close_user_connectionsis a new function that closes all connections that authenticated with a specific username
-
Client#disable_schema_definition_syncwas renamed toClient#disable_schema_definition_sync_on_node.This breaking change only applies to a function specific to Tanzu RabbitMQ 4.1, a series currently in development.
-
Client#enable_schema_definition_syncwas renamed toClient#enable_schema_definition_sync_on_node.This breaking change only applies to a function specific to Tanzu RabbitMQ 4.1, a series currently in development.
-
Client#disable_schema_definition_syncnow disables SDS on all cluster nodes.This function is specific to Tanzu RabbitMQ 4.1, a series currently in development.
-
Client#enable_schema_definition_syncnow enables SDS on all cluster nodes.This function is specific to Tanzu RabbitMQ 4.1, a series currently in development.
responses::Connection#channel_maxis now anOption<u16>because this metric wont' be available for, say, RabbitMQ Stream Protocol connections
-
New convenience functions for working with streams:
Client#get_stream_info,Client#delete_stream -
Client#declare_streamandrequests::StreamParamsfor convenient stream declaration
-
Initial support for Tanzu RabbitMQ Schema Definitions Sync (SDS) operations.
-
Initial support for Tanzu RabbitMQ Warm Standby Replication (WSR) operations.
-
Isolated test suite runs for each client.
To run only the async client tests, use
cargo test async --all-featuresTo run only the blocking client tests, use
cargo test blocking --all-features
- Async
Client#delete_*functions now correctly handleNotFoundresponses for idempotent deletes
api::Clientnow computes API endpoint path correctly (a slash was missing)
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.