I've updated my RPM building tools to match for RHEL 8 and 9. to
include anisble-core 1.14.2 andansible-corre 7.2.0, at:

     https://github.com/nkadel/ansiblblerepo

EPEL has been publishing an out-of-date and mismatched "ansible-6.3.0"
for RHEL 8 and RHEL 9, I'm not pleased with various parts of its
organization, I'll send the author a note with suggestions.

Nico Kadel-Garcia <[email protected]>

On Tue, Jan 31, 2023 at 5:26 PM Christian Adams <[email protected]> wrote:
>
> Hi all,
>
> We're happy to announce that the Ansible 7.2.0 package has been released!
>
> Ansible 7.2.0 will include ansible-core 2.14.2 as well as a curated set of
> Ansible collections to provide a vast number of modules and plugins.
>
> This is a major version update from Ansible 6.x which included
> ansible-core 2.13 and there may be backwards incompatibilities in the
> core playbook language.
>
> How to get it
> -------------
>
> This is available on PyPI and can be installed with pip:
>
> ```
> $ pip install ansible==7.2.0 --user
> ```
>
> The sources for this release can be found here:
>
> Release tarball:
> https://pypi.python.org/packages/source/a/ansible/ansible-7.2.0.tar.gz
> SHA256: 60e2c1a58f1ceb34a190b7c380f7b3386d1e7369061954b1f8b8ca3df76063cc
>
> Wheel package: 
> https://files.pythonhosted.org/packages/py3/a/ansible/ansible-7.2.0-py3-none-any.whl
> SHA256: 756a6d8fec6c19ccd7a00ad0f0cb18859f4ab77e0c5063f73a115f3fb75284aa
>
> What's new in Ansible 7
> ---------------------------
>
> Ansible 7 requires Python 3.9 on the controller, same as ansible-core 2.14.
>
> Variables are now evaluated lazily; only when they are actually used. For 
> example, in ansible-core 2.14 an expression ``{{ defined_variable or 
> undefined_variable }}`` does not fail on ``undefined_variable`` if the first 
> part of ``or`` is evaluated to ``True`` as it is not needed to evaluate the 
> second part.
>
> Collections added to Ansible 7:
> * ibm.spectrum_virtualize (version 1.9.0)
> * inspur.ispim (version 1.0.1)
> * purestorage.fusion (version 1.1.1)
> * vultr.cloud (version 1.1.0)
>
>
> The previously deprecated servicenow.servicenow collection has been removed.
>
> NOTE: Read the full Ansible 7 porting guide at 
> https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_7.rst
>  for complete details.
>
> * The changelog for ansible-core 2.14 installed by this release of
> ansible is available here:
> https://github.com/ansible/ansible/blob/stable-2.14/changelogs/CHANGELOG-v2.14.rst
>
> * Collections which have opted into being a part of the Ansible-7
> unified changelog will have an entry on this page:
> https://github.com/ansible-community/ansible-build-data/blob/main/7/CHANGELOG-v7.rst
>
> * For collections which have not opted into the unified changelog, you
> may find more information on https://galaxy.ansible.com or their
> source repository.
> For example, the community.crypto collection would be found at
> https://galaxy.ansible.com/community/crypto and you can find a link to
> the source repository under the "Repo" button at the top right.
>
> What's the schedule for new Ansible releases after 7.2.0?
> ---------------------------------------------------------
>
> * Please refer to the Ansible Project 7.0 Roadmap for more information about 
> the upcoming
> releases:
> https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_7.html
>
> * Please note that with the recent release of 2.14.0 
> https://groups.google.com/g/ansible-announce/c/JnolNZw-tdU, ansible 2.9, 
> ansible-base 2.10, and ansible-core 2.11 are end-of-life.
>
>
> Porting Help
> -------------
>
> A unified porting guide for collections which have opted-in is available here:
> https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_7.html
>
> Getting collection updates from Ansible 7 with older releases of ansible-core
> -----------------------------------------------------------------
>
> Ansible 6 includes ansible-core 2.13.x and users have expressed an interest
> in getting collection updates as they ship in the Ansible "batteries
> included" package while keeping an older version of ansible-core based
> on their needs and requirements.
>
> An ansible-galaxy requirements file based on the collections from
> Ansible 7 has been made available for this use case:
> https://github.com/ansible-community/ansible-build-data/blob/main/7/galaxy-requirements.yaml
>
> Once the requirements file has been downloaded, the collections can be
> installed by running:
> "ansible-galaxy collection install -r galaxy-requirements.yaml"
>
> On behalf of the Ansible community, thank you and happy automating!
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ansible-project/8e73e35e-b38c-4f46-90ab-1cf29103f35dn%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAOCN9ryWjwjUpMUjjhuuu-F1xCAHYPcxKSef8yr7V4kaMy3QXw%40mail.gmail.com.

Reply via email to