Chapter 3. Deprecated features
Deprecated functionality is still included in Ansible Automation Platform and continues to be supported during this version’s support cycle. However, the functionality will be removed in a future release of Ansible Automation Platform and is not recommended for new deployments.
The following table provides information about features that were deprecated in Ansible Automation Platform 2.5:
Component | Feature |
---|---|
Automation controller, | Tokens for the automation controller and the automation hub are deprecated. If you want to generate tokens, use the platform gateway to create them. The platform gateway is the service that handles authentication and authorization for the Ansible Automation Platform. It provides a single entry into the Ansible Automation Platform and serves the platform user interface, so you can authenticate and access all of the Ansible Automation Platform services from a single location. |
Automation controller and | All non-local authentications into the automation controller and automation hub are deprecated. Use the platform gateway to configure external authentications, such as SAML, LDAP, and RADIUS. |
Ansible-core |
The |
Ansible-core | The environment variable ANSIBLE_COLLECTIONS_PATHS is deprecated. Use the singular form ANSIBLE_COLLECTIONS_PATH instead. |
Ansible-core |
Old-style Ansible vars plug-ins that use the entry points |
Ansible-core | The STRING_CONVERSION_ACTION configuration option is deprecated as it is no longer used in the ansible-core code base. |
Ansible-core | The smart option for setting a connection plug-in is being removed as its main purpose of choosing between SSH and Paramiko protocols is now irrelevant. Select an explicit connection plug-in instead. |
Ansible-core |
The undocumented |
Ansible-core |
The string parameter |
Ansible-core |
The |
Ansible-core |
|
Ansible-core |
|
Automation execution environment | Execution environment-29 will be deprecated in the next major release after Ansible Automation Platform 2.5. |
Installer | The Ansible team is exploring ways to improve the installation of the Ansible Automation Platform on Red Hat Enterprise Linux, which may include changes to how components are deployed using RPM directly on the host OS. RPMs will be replaced by packages deployed into containers that are run via Podman; this is similar to how automation currently executes on Podman in containers (execution environments) on the host OS. Changes will be communicated through release notes, but removal will occur in major release versions of the Ansible Automation Platform. |
3.1. Deprecated API endpoints
API endpoints that will be removed in a future release either because their functionality is being removed or superseded with other capabilities. For example, with the platform moving to a centralized authentication system in the platform gateway, the existing authorization APIs in the automation controller and automation hub are being deprecated for future releases as all authentication operations should occur in the platform gateway.
Component | Endpoint | Capability |
---|---|---|
Automation controller |
| Token authentication is moving to the platform gateway. |
Automation hub |
| Moving to the platform gateway. |
Automation hub |
| Token authentication used for pulling collections will migrate to the platform gateway tokens. |
Automation controller |
| Moving to the platform gateway. |
Automation controller |
| Moving to the platform gateway. |
Automation controller |
| Moving to the platform gateway. |
Automation controller |
|
Controller-specific role definitions are moving to |
Automation controller | The following roles lists:
|
Controller-specific resource permissions are moving to |
Automation controller | The following object roles lists:
|
Controller-specific resource permissions are moving to |
Automation controller | The following resource access lists:
| No replacements yet. |