Ansible Versions

Ansible Versions
Written by Nilima PaulJanuary 15, 2022
13 min read
Nilima Paul

Technology Security Analyst

In this blog, We will discuss Ansible Versions.

Introduction to Ansible Versions

Ansible is a product organization device. It is likewise utilized for programming provisioning and setting up the board too. It is an open-source instrument. Ansible is known as a straightforward, agentless IT mechanization device moreover. In this subject, we will find out with regards to Ansible Versions.

List of Versions

Every Ansible version gets released every 4-6 month cycle depending upon the changes from version to version. For every new version, it can be tested before its release madis e available.

All the versions of Ansible are shown below and an explanation of each follows:

  • Before 1.9
  • 1.9 (1.9.1 to 1.9.6)
  • 2.0 (2.0.1 to 2.0.3)
  • 2.1 (2.1.1 to 2.1.6)
  • 2.2 (2.2.1 to 2.2.4)
  • 2.3 (2.3.1 to 2.3.4)
  • 2.4 (2.4.1 to 2.4.7)
  • 2.5 (2.5.1 to 2.5.15)
  • 2.6 (2.6.1 to 2.6.20)
  • 2.7 (2.7.1 to 2.7.16)
  • 2.8 (2.8.1 to 2.8.8)
  • 2.9 (2.9.1 to 2.9.4)

1. Version before 1.9

  • It began as a task, stop by different bug fixes and oversee updates from that point onwards. I began utilizing stock and playbooks.
  • Jobs were included Ansible 1.2 delivery
  • Improved conditionals as 'when' order with worked on factor support.
  • In 1.4 delivery around 33 new modules.
  • The extraordinary element in 1.5 is the 'verifiable localhost' object, therefore, we are no longer to add localhost to do ''hosts: localhost' or 'neighborhood activity' orders. Rather than these, we can utilize 'all' which alludes to every one of the servers in question.
  • 30+ extraordinary new modules included Ansible 1.6.
  • In 1.7 and 1.8 it prevailed in completely upheld windows alongside numerous upgrades.

2. Version 1.9

  • New modules and channels were added. New query, callback modules are likewise added.
  • Numerous new upgrades to the Amazon web administration modules and new docker enhancements were added.
  • Many bugs were fixed in the 1.9.1 variant which prompts improvement s3 module, administration module, the client module, and Unicode dealing with in a few module circumstances.
  • 9.2 thinks of safety fixes that check the hostnames coordinate testaments with HTTPS URLs, time region, prison, and chroot modules.
  • Change the yum module to introduce all bundles determined in a solitary exchange which fixes issues with conditions between bundles indicated by filename or URL.

3. Version 2.0

  • The new square mandates consider making task squares and exemption-like semantics.
  • Blunder taking care of improved, with more point by point parser messages.
  • meta: refresh_inventory has been added to compel perusing the stock in a playbook. Therefore, the stock contents can be re-executed yet don't constrain them to disregard any store they may utilize.
  • Utilizing 'su' as an honor heightening technique a few neighborhood associations work now.
  • Some 'ssh' is devalued as follows 'ansible_ssh_user' to ansible_user, 'ansible_ssh_host' to 'ansible_host' and 'ansible_ssh_port' to 'ansible_port'.
  • In 2.0 newlines now stay as determined in the layout record.
  • Callbacks shouldn't be duplicated as they are sent in the dynamic registry now.
  • Numerous API changes like callback, association, store, and query module APIs have changed.
  • Some new methodology modules were added which permit command over the progression of assignment execution per play and the default will be equivalent to previously.
  • Upgrades have been done on the side of extra shell types and in the code which is utilized to ascertain checksums for remote documents.

4. Version 2.1

  • New modules were added to Azure.
  • 'investigate' is the new methodology that has been added to permit per-task troubleshooting of playbooks.
  • Improved winrm contention approval and component sniffing alongside warm mistake taking care of fundamental parsing of stderr from the order line interface XML stream.
  • The retry record included had been re-carried out.
  • Ansible-console instrument, the office for modules to send back, capacity to send per-thing, capacity to channel realities, and so forth were added.
  • Extended and refactored support for Docker with new modules.
  • Numerous upgrades to existing modules, just as another Kubernetes module.

5. Version 2.2

  • New honor heightening turns into the strategy 'ksu'.
  • Windows 'async:' support for long-running assignments.
  • Jobs can now be remembered for the center of the assignment list through the new 'include_role'
  • 'meta' undertakings can now utilize conditionals.
  • Added help for paired modules and the capacity to indicate sequential clusters as a rundown as a piece of significant execution upgrades.
  • 'listen' include had added for modules, which permits errands to all the more effectively advise numerous overseers, just as making it simpler for controllers from decoupled jobs to be told.

6. Version 2.3

  • To whine about invalid contentions 'include_role' added.
  • To work with fresher arrivals of RHEL7, the hostname has been refreshed.
  • A significant security fix had done to stay away from supplier secret phrases spilling in the logs for the organization modules.
  • For empowering the order, 'metadata' is added to modules.
  • Most windows modules were normalized or potentially refactored by adding take a look at mode and diff support where conceivable.
  • Use of more presentpresent-dayork surveying API rather than select in the ssh association module to eliminate one restriction on the number of equal forks are possible on the frameworks.
  • Custom modules can be set in site-explicit catalogs and transported in jobs by permitting 'module_utils'.
  • Recognition of progress in docker picture when distributed ports are changed and can be dealt with.

7. Version 2.4

  • Old catchphrases incorporate/import are supplanted by the new watchwords.
  • For better administration, the stock classes have been parted.
  • The order line interface has been refreshed for better association with the stock.
  • For making stock some new stock modules were added simultaneously old stock configurations were being upheld by the modules.
  • A watchword 'request' added which permits the client to change the request while dispatching the errands.
  • A few boundaries in the 'bring' module were deployed alongside the 'unsafe_proxy' module which dodges roundabout import.
  • From YAML definitions, the design has been transformed from a hardcoded posting in the constants module to powerfully stacked.

8. Version 2.5

  • Many Network enhancements have occurred in this variant.
  • To supplant 'connection=local', the new modules 'network_cli' and 'netconf' were made.
  • Another channel is added to change the XML reaction over to the JSON object from an organization.
  • To work on standard director clients without crippling UAC on windows has improved the 'become me' rise process.
  • '- send out' is presently upheld by ansible-stock.
  • A site director can use to indicate modules to bar as a design record being added.
  • 'circle' added for the utilization of undertaking circles.

9. Version 2.6

  • 'encoding' has been added to the proper channels to determine the encoding of the string.
  • 'AnsibleParserError' has been fixed which was absent in the past forms.
  • 'argv' choice has been added to permit the order to be determined as a rundown.
  • VMware upheld modules and their boundaries were changed.
  • Above all, a few unused or superfluous highlights were eliminated. They resemble win_feature, win_package, and so forth,
  • 'always_run' changed to 'check_mode: no'

10. Version 2.7

  • 'ignore_unreachable' is another watchword added which permits in disregarding undertakings that flop because of inaccessible hosts.
  • Another module 'yumdnf' has been added which characterizes the common contention determination for both 'yum' and 'DNF' modules and they are currently at include equality.
  • Support for simplejson has been taken out.
  • Another component of locking a document has been added to acquire select access.
  • Most module changes and security fixes have occurred.

11. Version 2.8

  • '- become' has been changed to a module engineering.
  • Probably the best element is included in Ansible is 'Python mediator disclosure', which is the first python module that runs on the objective.
  • Some order line contentions were belittled. They resemble - sudo, - sudo-client, and so forth and they currently can be utilized as - become, - become-client, and so on
  • A k8s (Kubernetes) module has been added which diminishes the boundaries which are needed for products assignments in k8s.

12. Version 2.9

  • Among the various modules in the Ansible, they fixed the typos.
  • Supporting features are being added for the docker, Zabbix, and other IDEs.
  • Here in this latest version, some additional info about the collection namespace name restrictions.


Advancement is as yet under process for additional improvements and adding new elements to Ansible. It is most broadly utilizing ceaseless arrangement instruments as of late. The language utilized in the Ansible prearranging is easy to understand and can be seen without any problem. The programming language is utilized for it is 'YAML' which has acquired by python. All the more significantly, Ansible Tower fills in as an incredible extra to Ansible.

Ansible versions
Was this blog helpful?
You must be Logged in to comment
Code Block
Nilima Paul
Technology Security Analyst
201 Blog Posts
0 Discussion Threads
Trending Technologies
Frontend Development24
Backend Development20
Server Administration17
Linux Administration28
Data Center24
Penetration Testing16

Techiio is on the journey to build an ocean of technical knowledge, scouring the emerging stars in process and proffering them to the corporate world.

Follow us on:

Subscribe to get latest updates

You can unsubscribe anytime from getting updates from us
Developed and maintained by Wikiance
Developed and maintained by Wikiance