Hopeit.engine

Latest version: v0.25.4

Safety actively analyzes 688775 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 15

0.11.1

Not secure
______________
- Support for multiple steps with `Spawn` return values in a single step without needing to split using `SHUFFLE` steps.
Behaviour is equivalent to use nested python `AsyncGenerator` calls, but keeping the advantages of a more functional approach:
`__steps__` can be specified in sequence and functions implementing them do not need to reference each other.
- Limiting the number of steps to be executed in an event call to 1000 to prevent infinite loops. This limit is only
about the number of steps per event/item processed. The number of items generated by a `Spawn` function is not limited.

0.11.0

Not secure
______________
- Support for `settings` section in config:
- Each event settings (basic event setup, `logging`, `streams` settings) must be defined in a settings key with
the same name as event.
- Stream settings (like max_len, batch_size) must be configured in a settings section with the stream name as a key.
- EventContext has settings available on event execution time under `context.settings`.
- Custom settings can be added to each event settings section and parsed using a dataobject using
i.e. `context.settings(datatype=MySettings)`.
- Extra settings sections can be linked to each event context using `"setting_keys": ["section"]` in event config.
This section will be available to be parsed using `context.settings(key="section", datatype=MySettings)`

- Plugins:
- log_streamer: Moved configuration to `settings` section
- config_manager: Moved configuration to `settings` section
- apps_visualizer: Moved configuration to `settings` section

- Fixes:
- Explicitly specifying utf-8 encoding when saving and reading files
- log_streamer: fixed LogFileReader missing `super()` call on initialization

- Potential breaking changes:
- When using custom config files for plugins where settings where part of `env` section, you need
to update those files to use `settings` section instead, as defined in provided plugin config files.

0.10.2

Not secure
______________
- engine: updates for PyJWT 2.1.0 compatiblility.

0.10.1

Not secure
______________
- Plugins:
- redis-streams: updates for aioredis 2.0.0 compatiblility.
- redis-storage: updates for aioredis 2.0.0 compatiblility.

0.10.0

Not secure
______________
- Plugins:
- This release adds general support in several plugins to properly handle events that are plugged into app endpoints.

- Apps Client:
- Support for two authentication strategies: FORWARD_CONTEXT to propagate basic auth from client to server, and CLIENT_APP_PUBLIC_KEY to create Bearer token to be validated by server.
- Added support to configure and call plugin events that are plugged into app endpoints (plug_mode=ON_APP)

- Config Manager:
- Returns effective_events section prefixing event names with app_key and plugin_key

- Apps Visualizer:
- Handles edges between client apps calling ON_APP plugged events
- Live stats considers IGNORED events as a warning status
- Fixed Open API warning for multiple schemas with same name

- Log Streamer:
- Support to capture IGNORED (Unathorized) event calls

- Engine:
- Added tracking in EventContext for app_key and plugin_key, allowing logging those details as extra fields.

0.9.4

Not secure
_____________
- Fix: `apps-visualizer` plugin load effective_events from `config-manager` to avoid the need to install monitored apps in the same
running environment as `apps-visualizer`
- `config-manager` plugins, exposes effective_events (events with intermediate streams) as part of runtime app info.

Page 9 of 15

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.