Language and Page Formatting Options
Chapter 3. May 2022 release
This release includes a number of enhancements, additions, and fixes that have been implemented in the Red Hat Ansible Automation Platform.
3.1. Ansible Automation Platform 2.2
Red Hat Ansible Automation Platform simplifies the development and operation of automation workloads for managing enterprise application infrastructure lifecycles. It works across multiple IT domains including operations, networking, security, and development, as well as across diverse hybrid environments. Simple to adopt, use, and understand, Red Hat Ansible Automation Platform provides the tools needed to rapidly implement enterprise-wide automation, no matter where you are in your automation journey.
- Added the Automation Services Catalog as an on-prem component for the Ansible Automation Platform. Automation Services Catalog is is a Technology Preview supported feature in Ansible Automation Platform 2.2.
- Added support for RHEL 9 for automation controller, private automation hub, and private services catalog.
- Components of the Ansible Automation Platform now run with python 3.9 runtime.
- Ansible Automation Platform now deploys with PostgreSQL 13, Nginx 1.20 and Redis 6.
- The Ansible Automation Platform installer will now use certificates signed by a common certificate authority (CA) when certificates are not provided.
The Ansible Automation Platform installer is now provided as a package in the automation platform channels, allowing users to retrieve the installer without leaving their server using the
- Added Korean localization in the UI for automation controller, automation hub, and services catalog.
- Added ansible-core 2.13 to the ee-minimal and ee-supported containers.
- Added collection signing and verification as Technology Preview supported features in Ansible Automation hub.
- Ansible Builder now supports the verification of signatures in collection content when building execution environments (Technology Preview)
Other noteworthy developer tooling updates include the following:
ansible-lintis available as a technology preview. It is a command-line tool that further enhances the content creation experience by proven practices, patterns, and behaviors. See New features and changes for ansible-navigator for more information.
- Automation content navigator v2.0 now includes more features to create content more easily. See New features and changes for ansible-lint for more information.
- An updated VS Code extension provide language support for creating Ansible content, including smart auto-completion of related playbook content, syntax highlighting, jinja helpers, and direct integrations with supported tooling. See New features and enhancements for vscode-ansible for more information.
3.2. Automation Hub 4.5
Automation Hub allows you to discover and utilize new certified automation content from Red Hat Ansible and Certified Partners. On Ansible Automation Hub, you can discover and manage Ansible Collections, which is supported automation content developed by both partners and Red Hat for use cases such as cloud automation, network automation, security automation, and more.
- Added functionality for collection signing and verification in Ansible Builder.
Collection signing and verification are Technology Preview supported features.
3.3. Automation Services Catalog
Automation Services Catalog provides an easy way to extend automation in your Ansible controller to a broader user base. It offers multi-level approval to ensure extending automation is done safely. And, Role Based Access allows you to restrict automation access to specified users. Automation Services Catalog is the shop window into the Ansible Automation Platform.
Automation Services Catalog is a Technology Preview supported feature.
The following languages are supported for internalization:
- Private Automation Services Catalog can now be installed. Installation must be on a physical/virtual instance.
- Red Hat Single Sign-On can now be installed. Installation must be on a separate physical/virtual instance.
- Added role-based access for users and groups.
- Added ability to order products that contain job templates or workflows within portfolios.
- Extended metadata to describe products.
- Added functionality for an admin to share Portfolios to users.
- Added functionality to copy products and portfolios.
- Added option for multi-level approval process before a product can be executed.
- Added the approver role, who can approve, deny, or memo approval requests in a queue.
- Added ability to email approval requests.
- Added re-branding functionality to allow customers to change the default product icons and logos to match their organization.
3.4. Automation Controller 4.2
Automation controller replaces Ansible Tower. Automation controller introduces a distributed, modular architecture with a decoupled control and execution plane. The name change reflects these enhancements and the overall position within the Ansible Automation Platform suite.
Automation controller provides a standardized way to define, operate and delegate automation across the enterprise. It also introduces new, exciting technologies and an enhanced architecture that enables automation teams to scale and deliver automation rapidly to meet ever-growing business demand.
- Introduced the mesh visualizer feature that generates a visual representation of your mesh topology
- Automation controller now automatically mounts the system trust store in execution environments during job runs for VM-based installs
- Added log format for 4XX errors to allow customization of 4xx error messages that are produced when the API encounters an issue with a request
- Added ability to use labels in inventory files
- Added ability to flag users as superusers and auditors in SAML integration
- Automation controller now uses Python 3.9
See automation controller Release Notes for 4.x for a full list of new features and enhancements.
3.5. Automation Platform Operator 2.2
The Ansible Automation Platform Operator provides cloud-native, push-button deployment of new Ansible Automation Platform instances in your OpenShift environment.
image_pull_secret(string) variable has been deprecated and will no longer be supported in a future release. You should now use the
image_pull_secrets(array) variable on the spec when creating an Automation Hub or Automation Controller custom resource. This new variable allows you to specify multiple pull secrets as an array, for example:
spec: image_pull_secrets: - redhat-operators-pull-secret - my-other-pull-secret