Yaybu

Latest version: v3.1.1

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

Scan your dependencies

Page 6 of 6

0.1.7

Not secure
------------------

- Add some toys for people driving Yaybu from code without Yay
- Improve quick start documentation to stress idempotence
- Don't import yaybu.resources or yaybu.providers from yaybu package any more
- yaybu is now a namespace package
- You can declare your own resources and providers using the yaybu.resources
yaybu.providers entry points

0.1.6

Not secure
------------------

- A variable called yaybu.host is available from your configs
- Add Git support
- Added minimal RemoteRunner API
- --expand-only only shows resources key (more useful)
- More test coverage
- Documentation updates
- Support '.import: - ${foo}'

0.1.5

Not secure
------------------

- Logging is now via python logging module
- Audit log to syslog is working again
- Audit log is configurable through /etc/yaybu
- Added yaybu.core.debug to assist debugging yaybu in remote mode
- Can run network tests with TEST_NETWORK=1 ./bin/test discover
- New yaybu.harness module to house testing harness related code
- Tests have moved into sensible locations within yaybu module

0.1.4

Not secure
------------------

- EventState removes successfully applied updates on the fly, not just at the end
- Remove the simlog API and be as 'full-fat' as possible in simulate mode
- File provider will no longer log diffs when updating encrypted files ;)
- Every test that uses check_apply will also be tested for simulation
- Better use of python-magic: Use mimetypes and look for text/
- Use a stricter glob for identifying currently active sysv services
- EventState now records against id rather than home
- Test harness now enforces idempotence of check_apply
- Test harness now manages fakeroot by itself
- Fix logging issue for long resource ids
- More sensible default PATH
- Don't consider empty files to be binary
- Simplify logging, and fix logging of diffs
- Set environment from preexec function
- Lock down environment - don't leak environment from user
- Be more forgiving of mising PID files (Service provider)
- Better error handling in remote mode

0.1.3

Not secure
------------------

- RemoteRunner fixes
- Fix catching errors in remote
- Fix passing --resume and --no-resume to remote

0.1.2

Not secure
------------------

- Basic upstart, debian and 'simple' service providers
- Catches yay.errors.Error
- Add 'live logging' of shell steps (so you can see buildout progress)
- Add ability to watch files that might be updated by other providerss
- More tests
- Test env deals with races from cow-shell automatically
- Fix comment field of User provider
- Fix group and user bit of File/Directory/etc
- Resources are now referred to as Type[name] as otherwise Group and
User can very easily crash
- Jinja use is now more tolerant of unicode dictionary keys
- Observation state is now preserved on failure

Page 6 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.