Release Notes

torero 1.3.1

Bug Fixes

  • Fixed a bug where torero fails to recognize the location of a requirements.txt file and is therefore unable to install Python dependencies when running Python services.

torero 1.3.0

New Features: Private Registries, Secure Secrets, and More!

We’re excited to introduce several powerful new features that enhance security, flexibility, and usability. These updates make it easier to manage private registries, handle secrets securely, and streamline resource management. Let’s dive into what’s new!

🔒 Private Registry Support for Ansible & PyPi

Managing private package repositories just got easier! We now support both Ansible Galaxy and PyPi private registries, allowing seamless installation of modules and packages from restricted sources. This ensures better control over dependencies while keeping proprietary code secure.

pypi 

>_ torero create registry pypi -h

pypi 

>_ torero create registry ansible-galaxy -h

🛡️ Secure Secret Prompting in CLI

No more worrying about sensitive data exposure! Our CLI now prompts for passwords and secrets securely when inserting values, preventing them from being visible in terminal history or logs. This simple yet crucial improvement strengthens security across the board.

>_ torero create secret torero-v.13-secret --prompt-value
Enter the secret value:

📦 Ansible Role Management

We’ve expanded Ansible service capabilities by introducing support for installing and utilizing Ansible roles. This makes it easier to manage complex configurations and deployments, all within a streamlined workflow.

📜 Enhanced DSL for Import/Export

Our DSL (Domain-Specific Language) now supports importing and exporting Registries, Users, and Secrets, making it easier to move configurations across environments or back up essential settings with minimal effort.

📥 Importing Services from a Repository

We’ve introduced the ability to import services directly from a repository, making service deployment and integration smoother than ever. Now, pulling in services is a streamlined process, reducing manual work and improving automation.

>_ torero db import --repository https://github.com/itential/quick.git import.yml

These updates bring greater security, efficiency, and control to your workflows. Try them out and let us know what you think!

Improvements

For consistency, the syntax for running a service has been modified to now include the service keyword. Running a service will not resemble the following:

>_ torero run service python-script hello-torero

torero 1.2.0

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

Key Changes

1. Bug Fixes

  • 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).

2. Logging and Command Enhancements

  • 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.

3. Configuration Updates

  • 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.

torero 1.1.0

Key Features

1. Enhanced torero CLI

  • 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.

2. Database Migration Tools

  • 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

3. Distributed Execution/Runner Support

  • 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.

4. Etcd Data Store Integration

  • 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

Getting Started

CLI Enhancements

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

Database Migration

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.

Distributed Execution Setup

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

Keep Automating!

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