v0.5.0
What's Changed
Breaking Changes
-
Optional sync and async endpoints with environment variable NEREID_ASYNC_MODE
NEREID_ASYNC_MODE=none
(default) allows the app to be run as a single container apiNEREID_ASYNC_MODE=replace
will use the async endpoints instead of sync endpoints for the same routesNEREID_ASYNC_MODE=add
will add the async routes to api with the prefix set byNEREID_ASYNC_ROUTE_PREFIX
which defaults to"/async"- for backward compatibility use
NEREID_ASYNC_MODE=replace
-
config.yml format changed for nomographs. old way was like so:
met_table: file: met_data_20201218_1653.json volume_nomo: x_col: size_fraction t_col: ddt_hr y_col: capture_fraction flow_nomo: x_col: intensity_inhr t_col: tc_minutes y_col: capture_fraction
new way is like so:
met_table: file: met_data_20201218_1653.json nomographs: - file_key: volume_nomograph type: volume_capture constructor: VolumeNomograph x_col: size_fraction t_col: ddt_hr y_col: capture_fraction - file_key: flow_nomograph type: volume_capture constructor: FlowNomograph x_col: intensity_inhr t_col: tc_minutes y_col: capture_fraction
This allows for situations with more or fewer nomograph types that are needed for a project
-
redis
was is updated, now we need to use these connection vars:CELERY_BROKER_URL=redis://redis:6379/0 CELERY_RESULT_BACKEND=redis://redis:6379/0
Features
nereid
is now installable and importable as a standalone library.nereid.factory.create_app
can be used to create an instance and mount the nereid api into another asgi application.
Bugfixes and Refactoring
- removed the redis cache. redis is still used as a broker for async endpoints, but the redis cache is gone. too complex, too little benefit.
- patched an issue in the nested land surface case that was causing design volume not to be accumulated. This affected volume based regional facilities only, and only if the depth of the upstream delineations was greater than 1.
Full Changelog: v0.4.3...v0.5.0