Release Notes

torero 1.2.0

We're excited to announce torero 1.2.0, featuring some bug fixes, usability enhancements, and configuration updates.

Azure Repository: Fixed a bug that prevented pulling services from Azure repositories.
Local Mode Check: Added a check to prevent torero from running in local mode when another torero process is running as a server on the same machine.
Git Tags and SHAs: Fixed a bug to allow the usage of git tags and SHAs when specifying a --reference within a repository.
Database Import: Improved store logic to stop failures on large database imports (torero db import).

Store Logs: Moved store logs to TRACE level to prevent spam.
Help Menu: All commands will now be displayed in the torero help menu regardless of what application mode a user is in.

Runtime Data Directories: Added configuration variables TORERO_SERVER_RUNTIME_DATA_DIR and TORERO_RUNNER_RUNTIME_DATA_DIR to specify where virtual environments will be stored when running as a server. Default is /var/lib/torero.

Reorganized Application Contexts: Streamlined navigation commands within the CLI for easier access to various application components.
Auto-Complete for Resources: Improved tab completion for context menus containing services, secrets, decorators, and repositories, making CLI interactions more user friendly.

Local to Etcd Migration: New capability to migrate data from a local database to an etcd server, facilitating transitions to distributed architectures.
Flexible migration options:
Non-conflicting record migration
Forced migration with overwrite capabilities
Dry-run check option to preview potential changes

Introduced a cluster architecture model with core servers and runner nodes for improved scalability and availability across the execution layer.
Round-robin distribution of tasks among runner nodes within a cluster.
Support for multi-cluster setups, allowing for complex, distributed deployments.

Added support for etcd as a backend storage option, enabling distributed data management.
Configurable TLS security options for etcd connections:
Client-to-server transport security
Client-to-server authentication with client certificates

Update to the latest version to access improved auto-completion features.
Explore the reorganized application contexts for a more intuitive CLI experience.

To migrate from a local database to etcd:

torero db migrate local-to-etcd [--force] [--check]

Use --check to preview changes and --force to overwrite existing records if needed.

For detailed configuration steps, please refer to our resilient design documentation.

We're excited to see how our users leverage these new capabilities to build more scalable and efficient automations with torero!