Releases: torerodev/torero-container
v1.5.0
π torero 1.5.0
π Secrets In Services
torero's secret store just got much more useful! Starting in torero 1.5, secrets can now be injected into services via environment variables.
- Service Creation Integration: Secrets can now be associated with services at creation time using the --secret flag.
- Runtime Secret Injection: The new --set-secret flag allows dynamic secret injection during service execution.
- Decorator-Based Secret Management: Specify secret properties in JSON Schema decorators with the x-itential-secret-type and x-itential-secret-target annotations.
- This enhancement enables secure handling of sensitive data like API tokens, passwords, and AWS credentials while maintaining automation workflow integrity.
What's Changed
- Update publish.yml by @wcollins in #7
- fix/optimizations by @wcollins in #8
- fix/api-launcher by @wcollins in #9
- feature/run-mcp-service by @wcollins in #10
- feature/add-opentofu-build-time by @wcollins in #11
- fix/default-opentofu-version by @wcollins in #12
- feature/add-documentation-structure by @wcollins in #13
- feature/add-torero-api-service by @wcollins in #14
- Revert "feature/add-torero-api-service" by @wcollins in #15
- π¨ refactor: consolidate torero-api and torero-mcp services into contaβ¦ by @wcollins in #17
- feature/torero-ui by @wcollins in #18
- bugfix/runtime-service-stability by @wcollins in #19
- docs/refactor by @wcollins in #20
- release/v1.5.0 by @wcollins in #21
Full Changelog: v1.4.1...v1.5.0
v1.4.0
π torero 1.4.0
Support for latest torero release! The release notes for torero 1.4.0 are as follows:
π PyProject.toml Support (feature)
Python automation has evolved, and so has torero. With 1.4, we're moving beyond just supporting requirements.txt to embrace pyproject.toml β the modern standard for Python project configuration. This means your team can now leverage:
- Standardized Project Structures: Work with Python projects that follow current best practices without compromise
- Comprehensive Dependency Management: Specify dependencies directly in your pyproject.toml file and torero handles the rest
- Optional Dependencies: Install only what you need for specific automation tasks with the new --pyproj-optional-deps flag
- Script Execution: Run scripts defined in your project's [project.scripts] section using the new --pyproj-script flag
- See the pyproject.toml section of the Python document for more information.
π‘ Improvements
One can now specify a version of ansible-core in their requirements.txt for an Ansible service instead of just ansible.
v1.3.1
Summary
Refactored the torero container project to embrace open source standards and vendor-neutral technologies for improved accessibility and compatibility.
ποΈ Vendor Neutrality
Migrated from Dockerfile to Containerfile for OCI compliance
Switched base image to ghcr.io/linuxcontainers/debian-slim:latest
Updated build commands to use vendor-neutral container tools
π¦ Distribution & Registry
Moved from Docker Hub to GitHub Container Registry (GHCR)
Updated registry path: ghcr.io/torerodev/torero
Enhanced CI/CD compatibility with GitHub ecosystem
βοΈ Configuration Management
Added .env file support for version management
Externalized configuration variables
Improved EULA handling with TORERO_APPLICATION_AUTO_ACCEPT_EULA
What's Changed
New Contributors
Full Changelog: https://github.com/torerodev/torero-container/commits/v1.3.1