Release Announcement: ansible-creator v26.3.3

News & Announcements Ecosystem Releases
, , , , , ,
1

Hello everyone,

We are happy to announce the release of ansible-creator v26.3.3.

How to get it

You can install the latest version of all the ansible developer tools by running the following command:

python3 -m pip install -U ansible-dev-tools

This will install the following developer tools:

  • ansible-builder: a utility for building Ansible execution environments.
  • ansible-core: Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems.
  • ansible-creator: a utility for scaffolding Ansible project and content with recommended practices.
  • ansible-dev-environment: a utility for building and managing a virtual environment for Ansible content development.
  • ansible-lint: a utility to identify and correct stylistic errors and anti-patterns in Ansible playbooks and roles.
  • ansible-navigator a text-based user interface (TUI) for developing and troubleshooting Ansible content with execution environments.
  • ansible-sign: a utility for signing and verifying Ansible content.
  • molecule: a functional test runner for Ansible collections, playbooks and roles
  • pytest-ansible: a pytest testing framework extension that provides additional functionality for testing Ansible module and plugin Python code.
  • tox-ansible: an extension to the tox testing utility that provides additional functionality to check Ansible module and plugin Python code under different Python interpreters and Ansible core versions.

For a single tool, you can install it by running:

python3 -m pip -U install <project>==<release>

All ansible developer tools are also packaged in an image that you can use as a VS Code development container. The image is updated shortly after releases of any individual tool.
The community-dev-tools image is available on GitHub Container Registry.

podman run -it ghcr.io/ansible/community-ansible-dev-tools:latest

Sample devcontainer.json files are available in the ansible-dev-tools repository.

Release notes for ansible-creator v26.3.3

Features

  • feat: add image_build_tag workflow input for custom build tags (#568) @NilashishC
  • feat: add --registry-tls-verify CLI option for container registry TLS control (#564) @NilashishC
  • feat: add SCM servers support for private Git collection repositories (#559) @cidrblock
  • feat: make EE workflow configurable at runtime with dispatch inputs (#558) @NilashishC
  • feat: replace hardcoded hub URLs with generic galaxy_servers list (#556) @cidrblock
  • feat: wire ee_file_name through CLI so scaffolded EE projects use the custom filename (#557) @NilashishC
  • feat: add registry and image_name to EE configuration (#555) @cidrblock
  • feat: add ee_file_name to EEConfig for custom EE definition file names (#548) @cidrblock

Fixes

  • fix: enforce GITHUB_TOKEN for ghcr.io registry login (#570) @NilashishC
  • fix: update python interpreter to 3.12 for AAP 2.5 and unversioned official EE images (#562) @NilashishC
  • fix: add workflow_dispatch input defaults in ee-build template (#561) @NilashishC
  • ci(ee): verify buildah >= 1.24 before building with --build-arg (#552) @cidrblock
  • fix: omit empty additional_build_steps and simplify workflow inputs (#560) @NilashishC
  • fix(ee): remove broken curl-based Automation Hub token validation (#554) @cidrblock
  • fix: rename EEConfig JSON key from “name” to “ee_name” for CLI consistency (#553) @cidrblock
  • docs: fix EE project tree in installing.md (ci.yml → ee-build.yml) (#547) @cidrblock
  • fix: redesign ansible.cfg build flow — volume mount, ARG tokens, nothing in layers (#546) @cidrblock
  • fix: harden EE workflow — warn-only base image check, tighten token conditions (#545) @cidrblock
  • fix: Update ansible.cfg structure for official EE images (#544) @anusshukla

Maintenance

Release notes for all versions can be found in the changelog.