Chaostoolkit

Latest version: v1.19.0

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

Scan your dependencies

Page 6 of 11

1.2.0

Not secure
Added

- Support for structured logging [122][122]

[122]: https://github.com/chaostoolkit/chaostoolkit/issues/122

Changed

- Moved loading global controls back into `run_experiment` itself
[chaostoolkit-lib116][116]

[116]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/116

1.1.0

Not secure
Added

- Bump to Chaos Toolkit library 1.2.0
- Allow to declare and load controls from settings so they are globally
applied to all your runs [chaostoolkit-lib99][99]

In your settings file, at `~/.chaostoolkit-lib/settings.yaml` add, for
instance:

yaml
controls:
my-own-control:
provider:
module: mypackage.mycontrole_module
type: python


This will load `mypackage/mycontrole_module.py` from your `PYTHONPATH`
and use it as a [control][].
- Remove MacOSX build. Way too long for any benefits.
- Build against stable Python 3.7
- Ensure exit code is set in all cases

[control]: https://docs.chaostoolkit.org/reference/extending/create-control-extension/
[99]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/99

1.0.0

Not secure
Changed

- Cleaned up package metadata

1.0.0rc4

Not secure
Added

- Ensure requirements-dev.txt is bundled with the package
- Bumped chaostoolkit-lib to 1.0.0
- Ensure we don't create installation problem by forcing a specific version

1.0.0rc3

Not secure
Changed

- Bump to chaostoolkit-lib 1.0.0rc3

1.0.0rc2

Not secure
Changed

- Bump to chaostoolkit-lib 1.0.0rc2
- Enable MacOSX travis build to ensure Chaos Toolkit does build there

Page 6 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.