Releases: Flowminder/FlowKit
Releases · Flowminder/FlowKit
1.5.1
1.5.0
Added
- Added a flowclient
Queryclass to represent a FlowKit query #1980. - Added method
flowclient.Connection.update_token, to replace the API token for an existing connection.
Changed
- The names of flowclient functions for generating query specifications have been renamed to
<previous_name>_spec(e.g.flowclient.modal_locationis nowflowclient.modal_location_spec). flowclient.get_statusnow returns"not_running"(instead of raisingFileNotFoundError) if a query is not running or completed.- Flowclient functions
location_event_counts_spec,meaningful_locations_aggregate_spec,meaningful_locations_between_label_od_matrix_spec,meaningful_locations_between_dates_od_matrix_spec,flows_spec,unique_subscriber_counts_spec,location_introversion_spec,total_network_objects_spec,aggregate_network_objects_spec,spatial_aggregate_specandjoined_spatial_aggregate_spechave moved to theflowclient.aggregatessubmodule.
1.4.0
1.3.3
1.3.2
1.3.1
1.3.0
Added
- Improved UI for API permissions in FlowAuth.
Changed
- The format of user claims expected has changed from a dictionary, to string based format. FlowAPI now expects the claims key of any token to contain a list of scope strings.
- Permissions for joined spatial aggregates can now be set at a finer level in FlowAuth, to allow administrators to grant access only to specific combinations of query types at different aggregation units.
- FlowAuth no longer requires administrators to manually configure API routes, and will extract them from a FlowAPI server's open api specification.
- FlowAuth now uses structlog for log messages.
- FlowAPI no longer mandates a top level
aggregation_unitfield in query specifications. - FlowClient's
flowsandmodal_locationfunctions no longer require an aggregation unit.
Removed
- The poll type permission has been removed, and is implicitly granted by both read and get_result rights.
- FlowAuth no longer allows administrators to specify the name of a FlowAPI server, and will instead use the name specified in the server's open api specification.
1.2.1
1.2.0
Added
- FlowMachine can now use multiple FlowDB backends, redis instances or execution pools via the
flowmachine.connectionsorflowmachine.core.context.contextcontext managers. #391 flowmachine.core.connection.Connectionnow has aconn_idattribute, which is unique per database host. #391
@ -14,8 +24,6 @@ The format is based on Keep a Changelog.flowmachine.connectno longer returns aConnectionobject. The connection should be accessed viaflowmachine.core.context.get_db(). #391connection,redis, andthreadpoolare no longer available as attributes ofQuery, and should be accessed viaflowmachine.core.context.get_db(),flowmachine.core.context.get_redis()andflowmachine.core.context.get_executor(). #391