Standardized Environment Variables in AAP 2.6 — Migration Guide
By Luca Berton · Published 2024-01-01 · Category: troubleshooting
AAP 2.6 standardizes environment variables from component-specific names to unified AAP_ prefix. Learn what changed and how to update your configurations.
Introduction
AAP 2.6 introduces a significant quality-of-life improvement: standardized environment variable naming across all platform components. Collections now use a unified AAP_ prefix instead of component-specific prefixes.
What Changed
Before AAP 2.6
Each component had its own variable naming convention:
After AAP 2.6
A single, unified naming convention:
Module Variable Changes
Collections also standardize module-level variables:
Migration Steps
Step 1: Identify Current Variables
Search your playbooks and environment for component-specific variables:
Step 2: Update Environment Variables
Update your CI/CD pipelines, environment files, and vault entries:
Step 3: Update Playbooks
Replace component-specific module calls with the ansible.platform collection.
Step 4: Test
Verify all automation works with the new variable names before deploying to production.
Backward Compatibility
The old variable names may still work in AAP 2.6 for backward compatibility, but they are deprecated and will be removed in a future release. Migrate now to avoid issues later.
Conclusion
Standardized environment variables simplify configuration management and reduce confusion when working across platform components. Update your configurations now to benefit from the unified naming convention.
For more Ansible tutorials and guides, explore the complete article collection on Ansible Pilot.
Related Articles • Ansible Vault Guide • Ansible Template Guide • Ansible Environment Variables Guide
Category: troubleshooting