Deprecated features
Deprecated features are still included in Ansible Automation Platform 2.7 and continue to be supported during this version's support cycle. However, the feature will be removed in a future release of Ansible Automation Platform and is not recommended for new deployments.
- The
ee-cloud-services execution environment in Managed Application on Azure - Python 3.11 and earlier versions are deprecated.
-
The
ee-cloud-servicesexecution environment in Managed Application on Azure.
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.
- Recommended migration steps
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 execution environment.
- Build Custom execution envirnments using Ansible Builder: Use the
ee-supportedoree-minimalimage as your base in your execution-environment.ymlfile.
ee-supported images.
- Summary of support
- 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.
- Python 3.11 and earlier versions are deprecated
- Affected environments
- Supported Execution Environments
These environments typically include the full standard library and common pre-installed dependencies.
- Minimal Execution Environments
These are stripped-down, security-hardened environments used for Custom EE’s.
- Action required
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.
- Why this is happening
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.