Chapter 7. Deprecated features
- The ee-cloud-services execution environment in Managed Application on Azure
- Python 3.11 and earlier versions are deprecated
7.1. The ee-cloud-services execution environment in Managed Application on Azure Copy linkLink copied to clipboard!
Starting with the release of Ansible Automation Platform (AAP) 2.7, the ee-cloud-services execution environment will not be available in new deployments of Ansible Automation Platform on Microsoft Azure. Existing Ansible Automation Platform on Microsoft Azure customers are encouraged to transition their automation workflows to the ee-supported or build a new execution environment; the execution environment will remain until you choose to remove it.
7.1.1. Recommended migration steps Copy linkLink copied to clipboard!
To ensure your automation continues to run smoothly on version 2.7, follow these best practices:
-
Audit Current Job Templates: Identify which Job Templates currently use
ee-cloud-services. -
Test with ee-supported: Switch the Execution Environment on a test Job Template to
ee-supported. -
Identify Missing Dependencies: If your playbooks fail due to missing Python libraries (e.g.,
boto3,azure-mgmt-compute) or specific Ansible collections, you will need to create a custom EE. -
Build Custom EEs using Ansible Builder: Use the
ee-supportedoree-minimalimage as your base in yourexecution-environment.ymlfile.
For Managed Cloud customers, ensure your private automation hub is configured to sync the latest images from the Red Hat ecosystem to maintain access to the supported ee-supported images.
7.1.2. Summary of support Copy linkLink copied to clipboard!
-
Existing Installs: Upgraded environments may retain
ee-cloud-servicesfor a limited grace period, but it is considered "End of Life." -
Fresh Installs:
ee-supported&ee-minimalare the only cloud-focused EE provided out of the box. -
Event-Driven Ansible
ansible.eda.noopis deprecated and there will not be a replacement.
7.2. Python 3.11 and earlier versions are deprecated Copy linkLink copied to clipboard!
Support for Python 3.11 and all earlier versions is being phased out across all Supported Execution Environments and Minimal Execution Environments. To ensure security compliance and access to the latest performance optimizations, users must migrate to Python 3.12 or higher.
7.2.1. Affected environments Copy linkLink copied to clipboard!
1. Supported Execution Environments
These environments typically include the full standard library and common pre-installed dependencies.
2. Minimal Execution Environments
These are stripped-down, security-hardened environments used for Custom EE’s.
7.2.2. Action required Copy linkLink copied to clipboard!
Audit custom-built binaries. Python 3.11 minimal layers will no longer receive security vulnerability (CVE) patches.
Recommendation: Move to the python:3.12+ or equivalent Minimal EE instance.
7.2.3. Why this is happening Copy linkLink copied to clipboard!
Python 3.12+ offers significant improvements that older environments cannot support, specifically:
- Improved Error Messages: More precise tracebacks for faster debugging.
- Performance: Advancements in the Faster CPython project.
- Security: Removal of deprecated APIs and older TLS versions that are increasingly vulnerable.