Releases: typesafehub/conductr-cli
Releases · typesafehub/conductr-cli
Specify poll period for conduct logs command
PyInstaller fixes
Add http package as hidden import required to build conduct and sandbox command #550
Depend on dcos 0.5.5 cli
Cluster Backup and Restore
CLI now supports conduct backup
and conduct restore
to back and restore ConductR cluster state.
Also includes some fixes:
- Fix sandbox network interface alias calculation on linux when launching with 10 or more instances - #537
- Fail if docker run exits with non-zero, thus failing if haproxy fails to start in the sandbox - #538
- Support /32 CIDR notation, thus allowing better usability in special environments like virtual machines. Fix bug with
sandbox run --addr-range
breaking conduct load/run - #542 - Update DC/OS support to detect service names and pick the first one with "conductr" in the name - #543
- Ensure correct field is used for DC/OS service name - #544
- Add missing
return False
for HTTP error supression - #545
Fix license loading
Fixes
- Restore functionality to
conduct load-license
by removing base64 encoding of OAuth2Bearer
token
Fix native sandbox build
Fixes
- Ensure native executable generated in Windows is done using .spec files
Fix native sandbox build
Fixes
- Sandbox native executable: add semver library to hidden imports #525
Sandbox version notification and bug fixes
Various fixes
S3 Resolver, improvements, and bug fixes
Feature update
- Introduce S3 Resolver #490
Improvements
- Notify user of
conduct load -f
to reauthenticate #501 - Improved error reporting for OS X reverser dns lookup #496
- Enable Continuous Delivery as default feature #492
- Allow variable substitutions in
--env
arguments forbndl
tool #489
Fixes
- conduct load/deploy now reads the first bundle.conf file listed in the archive central directory #499
- CLI now ignores whitespace for resolver credentials #495
- Refactor bndl so that component configurations are modified more consistently between different input types #494
- Wait for bundle scale: do not immediately exit when encountering error #493