.png?sv=2022-11-02&spr=https&st=2024-11-22T15%3A33%3A40Z&se=2024-11-22T15%3A43%3A40Z&sr=c&sp=r&sig=%2BvZNDqKu2UkgPjPLJHZEq4ZKrwU0G1GFTvTHp%2Fd34oo%3D){kind=logo}
IAG 4.3.0
- 05 Nov 2024
-
DarkLight
-
PDF
IAG 4.3.0
- Updated on 05 Nov 2024
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This page contains information for new features, improvements, and fixes completed within Itential Automation Gateway 4.3 (IAG), as well as any other announcements or information that coincides as part of this release..
Introducing IAG 4.3
We are excited to announce that you can now run Ansible Playbooks on whichever version of Ansible you want in IAG 4.3. This frees your automation teams to develop Playbooks in their preferred version of Ansible and deploy them to the same installation of IAG without having to worry about Ansible version compatibility.
Note
Itential has changed the version number scheme for the Itential Automation Gateway (IAG) application from date-based versioning to semantic versioning. For an explanation of semantic versioning, please visit https://semver.org/. The latest release of IAG (as of August 2024) is IAG 4.3.0.
The change in the version number scheme provides clarity for customers who want to understand how future releases of IAG are backwards compatible with earlier releases. All future releases of IAG will follow the scheme MAJOR.MINOR.MTCE:
MAJOR: a change of the major number indicates incompatible API changes.
MINOR: a change of the minor number indicates a release with added functionality and a backwards compatible API.
MTCE: a change of MTCE number indicates a bug-fix release
IAG release 4.3 is fully backwards compatible with all currently supported IAG releases which includes IAG 2022.1, IAG 2023.1, IAG 2023.2, and IAG 2023.3.
IAG Feature Release Notes [4.3.0]
Support of Multiple Ansible Versions
IAG 4.3 gives customers the ability to specify which installed version of Ansible should be used to execute a particular Ansible Playbook in IAG; this can be configured on a per Playbook basis. This capability leverages the existing IAG Python vEnv capability releases in IAG 2023.3 to provide this feature. If no specific Ansible version is selected for a Playbook, that Playbook will execute in the default version of Ansible configured for IAG.
Refer to Support of Multiple Ansible Versions for more information.
Expanded Support for Authenticating to HashiCorp Vault Using AppRole Authentication
IAG 4.3 expands support for authenticating to HashiCorp Vault for retrieving secrets using the AppRole authentication mechanism. Support for retrieving secrets from HashiCorp Vault has not changed.
Was this article helpful?
