Spec-Zone.ru › Ansible

Ansible 8 Porting Guide

  • Playbook
  • Command Line
  • Deprecated
  • Modules

    • Modules removed
    • Deprecation notices
    • Noteworthy module changes
  • Plugins
  • Porting custom scripts
  • Networking
  • Porting Guide for v8.7.0

    • Breaking Changes
  • Porting Guide for v8.6.0

    • Added Collections
    • Major Changes
    • Deprecated Features
  • Porting Guide for v8.5.0

    • Deprecated Features
  • Porting Guide for v8.4.0

    • Major Changes
    • Deprecated Features
  • Porting Guide for v8.3.0

    • Added Collections
    • Major Changes
    • Deprecated Features
  • Porting Guide for v8.2.0

    • Known Issues
    • Breaking Changes
    • Major Changes
    • Deprecated Features
  • Porting Guide for v8.1.0

    • Known Issues
    • Breaking Changes
    • Major Changes
    • Removed Features
    • Deprecated Features
  • Porting Guide for v8.0.0

    • Added Collections
    • Known Issues
    • Breaking Changes
    • Major Changes
    • Removed Collections
    • Removed Features
    • Deprecated Features

Ansible 8 is based on Ansible-core 2.15.

We suggest you read this page along with the Ansible 8 Changelog to understand what updates you may need to make.

Playbook

  • Conditionals - due to mitigation of security issue CVE-2023-5764 in ansible-core 2.15.7, conditional expressions with embedded template blocks can fail with the message “Conditional is marked as unsafe, and cannot be evaluated.” when an embedded template consults data from untrusted sources like module results or vars marked !unsafe. Conditionals with embedded templates can be a source of malicious template injection when referencing untrusted data, and can nearly always be rewritten without embedded templates. Playbook task conditional keywords such as when and until have long displayed warnings discouraging use of embedded templates in conditionals; this warning has been expanded to non-task conditionals as well, such as the assert action.

    - name: task with a module result (always untrusted by Ansible)
      shell: echo "hi mom"
      register: untrusted_result
    
    # don't do it this way...
    # - name: insecure conditional with embedded template consulting untrusted data
    #   assert:
    #     that: '"hi mom" is in {{ untrusted_result.stdout }}'
    
    - name: securely access untrusted values directly as Jinja variables instead
      assert:
        that: '"hi mom" is in untrusted_result.stdout'
    

Command Line

  • The return code of ansible-galaxy search is now 0 instead of 1 and the stdout is empty when results are empty to align with other ansible-galaxy commands.

Deprecated

  • Providing a list of dictionaries to vars: is deprecated in favor of supplying a dictionary.

    Instead of:

    vars:
      - var1: foo
      - var2: bar
    

    Use:

    vars:
      var1: foo
      var2: bar
    

Modules

No notable changes

Modules removed

The following modules no longer exist:

  • No notable changes

Deprecation notices

No notable changes

Noteworthy module changes

No notable changes

Plugins

No notable changes

Porting custom scripts

No notable changes

Networking

No notable changes

Porting Guide for v8.7.0

Breaking Changes

Ansible-core

  • assert - Nested templating may result in an inability for the conditional to be evaluated. See the porting guide for more information.

Porting Guide for v8.6.0

Added Collections

  • ibm.storage_virtualize (version 2.1.0)

Major Changes

community.mysql

  • The community.mysql collection no longer supports ansible-core 2.12 and ansible-core 2.13. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing those versions. Both are or will soon be End of Life and if you are still using them, you should consider upgrading to the latest Ansible / ansible-core 2.15 or later as soon as possible (https://github.com/ansible-collections/community.mysql/pull/574).
  • mysql_role - the column_case_sensitive argument’s default value will be changed to true in community.mysql 4.0.0. If your playbook expected the column to be automatically uppercased for your roles privileges, you should set this to false explicitly (https://github.com/ansible-collections/community.mysql/issues/578).
  • mysql_user - the column_case_sensitive argument’s default value will be changed to true in community.mysql 4.0.0. If your playbook expected the column to be automatically uppercased for your users privileges, you should set this to false explicitly (https://github.com/ansible-collections/community.mysql/issues/577).

fortinet.fortios

  • Add new fortios version 7.4.1.
  • Format the contents in the changelog.yml file.
  • Update Ansible version from 2.9 to 2.14.
  • Update Q&A with a resolution for Ansible Always Sending GET/PUT Requests as POST Requests.
  • Update the requirement.txt file to specify the sphinx_rtd_theme==1.3.0
  • update the required Ansible version to 2.14.0 in the runtime.yml file.

Deprecated Features

  • The collection ibm.spectrum_virtualize has been renamed to ibm.storage_virtualize. For now, both collections are included in Ansible. The content in ibm.spectrum_virtualize will be replaced with deprecated redirects to the new collection in Ansible 10.0.0, and these redirects will eventually be removed from Ansible. Please update your FQCNs for ibm.spectrum_virtualize.

Porting Guide for v8.5.0

Deprecated Features

community.general

  • The next major release, community.general 8.0.0, will drop support for ansible-core 2.11 and 2.12, which have been End of Life for some time now. This means that this collection no longer supports Python 2.6 on the target. Individual content might still work with unsupported ansible-core versions, but that can change at any time. Also please note that from now on, for every new major community.general release, we will drop support for all ansible-core versions that have been End of Life for more than a few weeks on the date of the major release (https://github.com/ansible-community/community-topics/discussions/271, https://github.com/ansible-collections/community.general/pull/7259).
  • redfish_info, redfish_config, redfish_command - the default value 10 for the timeout option is deprecated and will change to 60 in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/7295).

Porting Guide for v8.4.0

Major Changes

fortinet.fortios

  • Improve the document for adding notes and examples in Q&A for modules using Integer number as the mkey.

Deprecated Features

  • The community.azure collection is officially unmaintained and has been archived. Therefore, it will be removed from Ansible 10. There is already a successor collection azure.azcollection in the community package which should cover the same functionality (https://github.com/ansible-community/community-topics/issues/263).
  • The hpe.nimble collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/254).

Ansible-core

  • vault and unfault filters - the undocumented vaultid parameter is deprecated and will be removed in ansible-core 2.20. Use vault_id instead.

ansible.netcommon

  • libssh - the ssh_*_args options are now marked that they will be removed after 2026-01-01.

Porting Guide for v8.3.0

Added Collections

  • telekom_mms.icinga_director (version 1.34.1)

Major Changes

fortinet.fortios

  • Add readthedocs.yaml file.
  • Update Q&A regarding setting up FortiToken multi-factor authentication;

Deprecated Features

  • The collection t_systems_mms.icinga_director has been renamed to telekom_mms.icinga_director. For now both collections are included in Ansible. The content in t_systems_mms.icinga_director will be replaced with deprecated redirects to the new collection in Ansible 9.0.0, and these redirects will eventually be removed from Ansible. Please update your FQCNs for t_systems_mms.icinga_director.
  • The netapp.azure collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/234).
  • The netapp.elementsw collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/235).
  • The netapp.um_info collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/244).
  • The ngine_io.vultr collection is officially unmaintained and has been archived. Therefore, it will be removed from Ansible 9. There is already a successor collection vultr.cloud (using the recent v2 Vultr API) in the community package which covers the functionality but might not have compatible syntax (https://github.com/ansible-community/community-topics/issues/257).

community.crypto

  • get_certificate - the default false of the asn1_base64 option is deprecated and will change to true in community.crypto 3.0.0 (https://github.com/ansible-collections/community.crypto/pull/600).

community.general

  • ejabberd_user - deprecate the parameter logging in favour of producing more detailed information in the module output (https://github.com/ansible-collections/community.general/pull/7043).

community.postgresql

  • postgresql_lang - the module has been deprecated and will be removed in community.postgresql 4.0.0. Please use the postgresql_ext module instead (https://github.com/ansible-collections/community.postgresql/issues/559).

Porting Guide for v8.2.0

Known Issues

Ansible-core

  • ansible-test - The Fedora 37 remote is known to occasionally hang during boot. It is no longer routinely tested as a result. If possible, use the Fedora 38 remote instead.

community.crypto

  • Ansible markup will show up in raw form on ansible-doc text output for ansible-core before 2.15. If you have trouble deciphering the documentation markup, please upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on https://docs.ansible.com/ansible/devel/collections/community/crypto/.

community.hrobot

  • Ansible markup will show up in raw form on ansible-doc text output for ansible-core before 2.15. If you have trouble deciphering the documentation markup, please upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on https://docs.ansible.com/ansible/devel/collections/community/hrobot/.

community.routeros

  • Ansible markup will show up in raw form on ansible-doc text output for ansible-core before 2.15. If you have trouble deciphering the documentation markup, please upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on https://docs.ansible.com/ansible/devel/collections/community/routeros/.

community.sops

  • Ansible markup will show up in raw form on ansible-doc text output for ansible-core before 2.15. If you have trouble deciphering the documentation markup, please upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on https://docs.ansible.com/ansible/devel/collections/community/sops/.

Breaking Changes

hetzner.hcloud

  • hcloud-python 1.20.0 is now required for full compatibility

Major Changes

chocolatey.chocolatey

  • win_chocolatey - add options for specifying checksums
  • win_chocolatey_facts - add filter / gather_subset option

community.vmware

  • vmware_vasa - added a new module to register/unregister a VASA provider
  • vmware_vasa_info - added a new module to gather the information about existing VASA provider(s)

grafana.grafana

  • Addition of Grafana Server role by @gardar
  • Configurable agent user groups by @NormanJS
  • Grafana Plugins support on-prem Grafana installation by @ishanjainn
  • Updated Service for flow mode by @bentonam

Deprecated Features

  • The collection community.sap has been renamed to community.sap_libs. For now both collections are included in Ansible. The content in community.sap will be replaced with deprecated redirects to the new collection in Ansible 9.0.0, and the collection will be removed from Ansible 10 completely. Please update your FQCNs for community.sap.
  • The deprecated servicenow.servicenow collection has been removed from Ansible 7, but accidentally re-added to Ansible 8. It will be removed again from Ansible 9 (https://github.com/ansible-community/community-topics/issues/246).

community.general

  • flowdock - module relies entirely on no longer responsive API endpoints, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6930).
  • proxmox - old feature flag proxmox_default_behavior will be removed in community.general 10.0.0 (https://github.com/ansible-collections/community.general/pull/6836).
  • stackdriver - module relies entirely on no longer existent API endpoints, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6887).
  • webfaction_app - module relies entirely on no longer existent API endpoints, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6909).
  • webfaction_db - module relies entirely on no longer existent API endpoints, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6909).
  • webfaction_domain - module relies entirely on no longer existent API endpoints, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6909).
  • webfaction_mailbox - module relies entirely on no longer existent API endpoints, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6909).
  • webfaction_site - module relies entirely on no longer existent API endpoints, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6909).

junipernetworks.junos

  • junos_ospfv2 - add deprecate warning for area_range.
  • add deprecate warning for junos_acl_interfaces key for junos facts results.

Porting Guide for v8.1.0

Known Issues

community.dns

  • Ansible markup will show up in raw form on ansible-doc text output for ansible-core before 2.15. If you have trouble deciphering the documentation markup, please upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on https://docs.ansible.com/ansible/devel/collections/community/dns/.

community.docker

  • Ansible markup will show up in raw form on ansible-doc text output for ansible-core before 2.15. If you have trouble deciphering the documentation markup, please upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on https://docs.ansible.com/ansible/devel/collections/community/docker/.

community.general

  • Ansible markup will show up in raw form on ansible-doc text output for ansible-core before 2.15. If you have trouble deciphering the documentation markup, please upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on https://docs.ansible.com/ansible/devel/collections/community/general/ (https://github.com/ansible-collections/community.general/pull/6539).

dellemc.openmanage

  • idrac_redfish_storage_contoller - Issue(256164) - If incorrect value is provided for one of the attributes in the provided attribute list for controller configuration, then this module does not exit with error.
  • ome_device_network_services - Issue(212681) - The module does not provide a proper error message if unsupported values are provided for the following parameters- port_number, community_name, max_sessions, max_auth_retries, and idle_timeout.
  • ome_device_power_settings - Issue(212679) - The module displays the following message if the value provided for the parameter power_cap is not within the supported range of 0 to 32767, Unable to complete the request because PowerCap does not exist or is not applicable for the resource URI.
  • ome_smart_fabric_uplink - Issue(186024) - Despite the module supported by OpenManage Enterprise Modular, it does not allow the creation of multiple uplinks of the same name. If an uplink is created using the same name as an existing uplink, the existing uplink is modified.

Breaking Changes

  • Please note that the breaking change announced in the dellemc.enterprise_sonic changelog below is from dellemc.enterprise_sonic 2.1.0 and was reverted in dellemc.enterprise_sonic 2.2.0, so it is not contained in Ansible 8. For technical reasons, this entry is still shown here.

dellemc.enterprise_sonic

  • sonic_aaa - Add default_auth attribute to the argspec to replace the deleted group and local attributes. This change allows for ordered login authentication. (https://github.com/ansible-collections/dellemc.enterprise_sonic/pull/195).

Major Changes

cloudscale_ch.cloud

  • Bump minimum required Ansible version to 2.13.0

fortinet.fortimanager

  • Support all FortiManager versions in 6.2, 6.4, 7.0, 7.2 and 7.4. 139 new modules.
  • Support token based authentication.

fortinet.fortios

  • Improve the no_log feature in some modules;
  • Improve the documentation and example for seq_num in fortios_router_static;
  • Improve the documentation for member_path in all the modules;
  • Support new FOS versions.

Removed Features

community.ciscosmb

  • remove testing for Python 2.6 nad 2.7
  • remove testing for ansible 2.9

Deprecated Features

  • The gluster.gluster collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/225).

amazon.aws

  • s3_object - support for passing object keys with a leading / has been deprecated and will be removed in a release after 2025-12-01 (https://github.com/ansible-collections/amazon.aws/pull/1549).

community.ciscosmb

  • support for Python 2.6 nad 2.7
  • support for ansible 2.9

community.general

  • CmdRunner module utils - deprecate cmd_runner_fmt.as_default_type() formatter (https://github.com/ansible-collections/community.general/pull/6601).
  • MH VarsMixin module utils - deprecates VarsMixin and supporting classes in favor of plain vardict module util (https://github.com/ansible-collections/community.general/pull/6649).
  • cpanm - value compatibility is deprecated as default for parameter mode (https://github.com/ansible-collections/community.general/pull/6512).
  • redhat module utils - the module_utils.redhat module is deprecated, as effectively unused: the Rhsm, RhsmPool, and RhsmPools classes will be removed in community.general 9.0.0; the RegistrationBase class will be removed in community.general 10.0.0 together with the rhn_register module, as it is the only user of this class; this means that the whole module_utils.redhat module will be dropped in community.general 10.0.0, so importing it without even using anything of it will fail (https://github.com/ansible-collections/community.general/pull/6663).
  • redhat_subscription - the autosubscribe alias for the auto_attach option has been deprecated for many years, although only in the documentation. Officially mark this alias as deprecated, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6646).
  • redhat_subscription - the pool option is deprecated in favour of the more precise and flexible pool_ids option (https://github.com/ansible-collections/community.general/pull/6650).
  • rhsm_repository - state=present has not been working as expected for many years, and it seems it was not noticed so far; also, “presence” is not really a valid concept for subscription repositories, which can only be enabled or disabled. Hence, mark the present and absent values of the state option as deprecated, slating them for removal in community.general 10.0.0 (https://github.com/ansible-collections/community.general/pull/6673).

microsoft.ad

  • Deprecating support for Server 2012 and Server 2012 R2. These OS versions are reaching End of Life status from Microsoft and support for using them in Ansible are nearing its end.

purestorage.fusion

  • fusion_api_client - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_array - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_az - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_hap - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_hap - parameters nqn, wwns, host_password, host_user, target_password`and `target_user were deprecated
  • fusion_hw - FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_info - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_info - ‘hosts’ subset is deprecated in favor of ‘host_access_policies’ and will be removed in the version 2.0.0
  • fusion_info - ‘interfaces’ subset is deprecated in favor of ‘network_interfaces’ and will be removed in the version 2.0.0
  • fusion_info - ‘zones’ subset is deprecated in favor of ‘availability_zones’ and will be removed in the version 2.0.0
  • fusion_ni - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_nig - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_pg - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_pp - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_ra - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_region - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_sc - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_se - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_se - endpoint_type parameter is now deprecated and will be removed in version 2.0.0
  • fusion_ss - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_tenant - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_tn - FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_ts - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0
  • fusion_volume - ‘app_id’ and ‘key_file’ parameters are deprecated in favor of ‘issuer_id’ and ‘private_key_file’ parameters and will be removed in the version 2.0.0, FUSION_APP_ID and FUSION_HOST env variables are deprecated in favor of FUSION_ISSUER_ID and FUSION_HOST and will be removed in the version 2.0.0

Porting Guide for v8.0.0

Added Collections

  • dellemc.powerflex (version 1.6.0)
  • dellemc.unity (version 1.6.0)
  • grafana.grafana (version 2.0.0)
  • microsoft.ad (version 1.1.0)
  • servicenow.servicenow (version 1.0.6)

Known Issues

Ansible-core

  • ansible-test - Additional configuration may be required for certain container host and container combinations. Further details are available in the testing documentation.
  • ansible-test - Custom containers with VOLUME instructions may be unable to start, when previously the containers started correctly. Remove the VOLUME instructions to resolve the issue. Containers with this condition will cause ansible-test to emit a warning.
  • ansible-test - Systems with Podman networking issues may be unable to run containers, when previously the issue went unreported. Correct the networking issues to continue using ansible-test with Podman.
  • ansible-test - Unit tests for collections do not support pytest assertion rewriting on Python 2.7.
  • ansible-test - Using Docker on systems with SELinux may require setting SELinux to permissive mode. Podman should work with SELinux in enforcing mode.
  • dnf5 - The DNF5 package manager currently does not provide all functionality to ensure feature parity between the existing dnf and the new dnf5 module. As a result the following dnf5 options are effectively a no-op: cacheonly, enable_plugin, disable_plugin and lock_timeout.

cisco.meraki

  • meraki_network - Updated documentation for local_status_page_enabled and remote_status_page_enabled as these no longer work.

community.docker

  • The modules and plugins using the vendored code from Docker SDK for Python currently do not work with requests 2.29.0 and/or urllib3 2.0.0. The same is currently true for the latest version of Docker SDK for Python itself (https://github.com/ansible-collections/community.docker/issues/611, https://github.com/ansible-collections/community.docker/pull/612).
  • docker_api connection plugin - does not work with TCP TLS sockets! This is caused by the inability to send an close_notify TLS alert without closing the connection with Python’s SSLSocket (https://github.com/ansible-collections/community.docker/issues/605, https://github.com/ansible-collections/community.docker/pull/621).
  • docker_container_exec - does not work with TCP TLS sockets when the stdin option is used! This is caused by the inability to send an close_notify TLS alert without closing the connection with Python’s SSLSocket (https://github.com/ansible-collections/community.docker/issues/605, https://github.com/ansible-collections/community.docker/pull/621).

community.routeros

  • api_modify - when limits for entries in queue tree are defined as human readable - for example 25M -, the configuration will be correctly set in ROS, but the module will indicate the item is changed on every run even when there was no change done. This is caused by the ROS API which returns the number in bytes - for example 25000000 (which is inconsistent with the CLI behavior). In order to mitigate that, the limits have to be defined in bytes (those will still appear as human readable in the ROS CLI) (https://github.com/ansible-collections/community.routeros/pull/131).
  • api_modify, api_info - routing ospf area, routing ospf area range, routing ospf instance, routing ospf interface-template paths are not fully implemented for ROS6 due to the significant changes between ROS6 and ROS7 (https://github.com/ansible-collections/community.routeros/pull/131).

dellemc.openmanage

  • idrac_firmware - Issue(249879) - Firmware update of iDRAC9-based Servers fails if SOCKS proxy with authentication is used.
  • idrac_os_deployment- Issue(260496) - OS installation will support only NFS and CIFS share to store the custom ISO in the destination_path, HTTP/HTTPS/FTP not supported
  • idrac_redfish_storage_contoller - Issue(256164) - If incorrect value is provided for one of the attributes in the provided attribute list for controller configuration, then this module does not exit with error.
  • idrac_user - Issue(192043) The module may error out with the message Unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress. Wait for the job to complete and run the task again.
  • idrac_user - Issue(192043) The module may error out with the message unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress. Wait for the job to complete and run the task again.
  • ome_application_alerts_syslog - Issue(215374) - The module does not provide a proper error message if the destination_address is more than 255 characters.
  • ome_device_network_services - Issue(212681) - The module does not provide a proper error message if unsupported values are provided for the following parameters- port_number, community_name, max_sessions, max_auth_retries, and idle_timeout.
  • ome_device_network_services - Issue(212681) - The module does not provide a proper error message if unsupported values are provided for the parameters- port_number, community_name, max_sessions, max_auth_retries, and idle_timeout.
  • ome_device_power_settings - Issue(212679) - The module displays the following message if the value provided for the parameter power_cap is not within the supported range of 0 to 32767, Unable to complete the request because PowerCap does not exist or is not applicable for the resource URI.
  • ome_inventory - Issue(256257) - All hosts are not retrieved for Modular System group and corresponding child groups.
  • ome_inventory - Issue(256589) - All hosts are not retrieved for Custom Groups group and corresponding child groups.
  • ome_inventory - Issue(256593) - All hosts are not retrieved for PLUGIN GROUPS group and corresponding child groups.
  • ome_smart_fabric_uplink - Issue(186024) - Despite the module supported by OpenManage Enterprise Modular, it does not allow the creation of multiple uplinks of the same name. If an uplink is created using the same name as an existing uplink, the existing uplink is modified.
  • ome_smart_fabric_uplink - Issue(186024) - The module does not allow the creation of multiple uplinks of the same name even though it is supported by OpenManage Enterprise Modular. If an uplink is created using the same name as an existing uplink, the existing uplink is modified.

Breaking Changes

Ansible-core

  • ansible-doc - no longer treat plugins in collections whose name starts with _ as deprecated (https://github.com/ansible/ansible/pull/79362).
  • ansible-test - Integration tests which depend on specific file permissions when running in an ansible-test managed host environment may require changes. Tests that require permissions other than 755 or 644 may need to be updated to set the necessary permissions as part of the test run.
  • ansible-test - The vcenter test plugin now defaults to using a user-provided static configuration instead of the govcsim simulator for collections. Set the ANSIBLE_VCSIM_CONTAINER environment variable to govcsim to use the simulator. Keep in mind that the simulator is deprecated and will be removed in a future release.
  • ansible-test sanity - previously plugins and modules in collections whose name started with _ were treated as deprecated, even when they were not marked as deprecated in meta/runtime.yml. This is no longer the case (https://github.com/ansible/ansible/pull/79362).
  • ansible-test validate-modules - Removed the missing-python-doc error code in validate modules, missing-documentation is used instead for missing PowerShell module documentation.

amazon.aws

  • The amazon.aws collection has dropped support for botocore<1.25.0 and boto3<1.22.0. Most modules will continue to work with older versions of the AWS SDK, however compatibility with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/amazon.aws/pull/1342).
  • amazon.aws - compatibility code for Python < 3.6 has been removed (https://github.com/ansible-collections/amazon.aws/pull/1257).
  • ec2_eip - the previously deprecated instance_id alias for the device_id parameter has been removed. Please use the device_id parameter name instead (https://github.com/ansible-collections/amazon.aws/issues/1176).
  • ec2_instance - the default value for instance_type has been removed. At least one of instance_type or launch_template must be specified when launching new instances (https://github.com/ansible-collections/amazon.aws/pull/1315).
  • ec2_vpc_dhcp_options - the new_options return value has been deprecated after being renamed to dhcp_config. Please use the dhcp_config or dhcp_options return values (https://github.com/ansible-collections/amazon.aws/pull/1327).
  • ec2_vpc_endpoint - the policy_file parameter has been removed. I(policy) with a file lookup can be used instead (https://github.com/ansible-collections/amazon.aws/issues/1178).
  • ec2_vpc_net - the classic_link_enabled return value has been removed. Support for EC2 Classic networking was dropped by AWS (https://github.com/ansible-collections/amazon.aws/pull/1374).
  • ec2_vpc_net_info - the classic_link_dns_status return value has been removed. Support for EC2 Classic networking was dropped by AWS (https://github.com/ansible-collections/amazon.aws/pull/1374).
  • ec2_vpc_net_info - the classic_link_enabled return value has been removed. Support for EC2 Classic networking was dropped by AWS (https://github.com/ansible-collections/amazon.aws/pull/1374).
  • module_utils.cloud - the previously deprecated CloudRetry.backoff has been removed. Please use CloudRetry.exponential_backoff or CloudRetry.jittered_backoff instead (https://github.com/ansible-collections/amazon.aws/issues/1110).

ansible.netcommon

  • NetworkConnectionBase now inherits from PersistentConnectionBase in ansible.utils. As a result, the minimum ansible.utils version has increased to 2.7.0.
  • NetworkTemplate is no longer importable from ansible_collections.ansible.netcommon.plugins.module_utils.network.common and should now be found at its proper location ansible_collections.ansible.netcommon.plugins.module_utils.network.common.rm_base.network_template
  • ResourceModule is no longer importable from ansible_collections.ansible.netcommon.plugins.module_utils.network.common and should now be found at its proper location ansible_collections.ansible.netcommon.plugins.module_utils.network.common.rm_base.resource_module
  • VALID_MASKS, is_masklen, is_netmask, to_bits, to_ipv6_network, to_masklen, to_netmask, and to_subnet are no longer importable from ansible_collections.ansible.netcommon.plugins.module_utils.network.common.utils and should now be found at their proper location ansible.module_utils.common.network

community.aws

  • The community.aws collection has dropped support for botocore<1.25.0 and boto3<1.22.0. Most modules will continue to work with older versions of the AWS SDK, however compatability with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/community.aws/pull/1743).
  • aws_ssm - the AWS SSM plugin was incorrectly prepending sudo to most commands. This behaviour was incorrect and has been removed. To execute commands as a specific user, including the root user, the become and become_user directives should be used. See the Ansible documentation for more information (https://github.com/ansible-collections/community.aws/issues/853).
  • codebuild_project - tags parameter now accepts a dict representing the tags, rather than the boto3 format (https://github.com/ansible-collections/community.aws/pull/1643).

community.general

  • If you are not using this collection as part of Ansible, but installed (and/or upgraded) community.general manually, you need to make sure to also install community.sap_libs if you are using any of the sapcar_extract, sap_task_list_execute, and hana_query modules. Without that collection installed, the redirects for these modules do not work.
  • ModuleHelper module utils - when the module sets output variables named msg, exception, output, vars, or changed, the actual output will prefix those names with _ (underscore symbol) only when they clash with output variables generated by ModuleHelper itself, which only occurs when handling exceptions. Please note that this breaking change does not require a new major release since before this release, it was not possible to add such variables to the output due to a bug (https://github.com/ansible-collections/community.general/pull/5765).
  • gconftool2 - fix processing of gconftool-2 when key does not exist, returning null instead of empty string for both value and previous_value return values (https://github.com/ansible-collections/community.general/issues/6028).
  • gitlab_runner - the default of access_level_on_creation changed from false to true (https://github.com/ansible-collections/community.general/pull/6428).
  • ldap_search - convert all string-like values to UTF-8 (https://github.com/ansible-collections/community.general/issues/5704, https://github.com/ansible-collections/community.general/pull/6473).
  • nmcli - the default of the hairpin option changed from true to false (https://github.com/ansible-collections/community.general/pull/6428).
  • proxmox - the default of the unprivileged option changed from false to true (https://github.com/ansible-collections/community.general/pull/6428).

community.hashi_vault

  • Support for ansible-core 2.11 and 2.12 has been removed (https://github.com/ansible-collections/community.hashi_vault/issues/340).
  • The minimum version of hvac for community.hashi_vault is now 1.1.0 (https://github.com/ansible-collections/community.hashi_vault/issues/324).
  • hashi_vault lookup - duplicate option entries in the term string now raises an exception instead of a warning (https://github.com/ansible-collections/community.hashi_vault/issues/356).

community.zabbix

  • agent role - removed support for Darwin, Amazon, Fedora, XCP-ng, Suse, Mint, and Sangoma operating systems
  • agent role - removed support for zabbix_create_host and replaced it with zabbix_agent_host_state
  • agent role - removed support for zabbix_create_hostgroup and replaced it with zabbix_agent_hostgroups_state
  • agent role - removed support for zabbix_http_password, zabbix_api_http_password, zabbix_api_pass, and zabbix_api_login_pass and replaced it with zabbix_api_login_pass
  • agent role - removed support for zabbix_http_user, zabbix_api_http_user, zabbix_api_user, and zabbix_api_login_user and replaced it with zabbix_api_login_user
  • agent role - removed support for zabbix_inventory_mode and replaced it with zabbix_agent_inventory_mode
  • agent role - removed support for zabbix_link_templates adn replaced it with zabbix_agent_link_templates
  • agent role - removed support for zabbix_macros and replaced it with zabbix_agent_macros
  • agent role - removed support for zabbix_proxy and replaced it with zabbix_agent_proxy
  • agent role - removed support for zabbix_update_host and replaced it with zabbix_agent_host_update
  • all modules - dropped support of Zabbix versions < 6.0
  • all roles - removed support for the zabbix_version variable.
  • all roles - removed support for all versions of Zabbix < 6.0.
  • all roles - removed support for installation from epel and non-standard repositories
  • dropped support of zabbix-api to make REST API calls to Zabbix
  • proxy role - removed support for zabbix_database_creation and replaced it with zabbix_proxy_database_creation
  • proxy role - removed support for zabbix_database_sqlload and replaced it with zabbix_proxy_database_sqlload
  • proxy role - removed support for zabbix_selinux and replaced it with zabbix_proxy_selinux
  • server role - removed support for zabbix_server_mysql_login_password and replaced with zabbix_server_dbpassword
  • server role - removed support for zabbix_server_mysql_login_user and replaced with zabbix_server_dbuser
  • stopped supporting Ansible < 2.12
  • stopped supporting Python < 3.9
  • zabbix_action - message parameter renamed to op_message
  • zabbix_group_facts module - removed in favour of zabbix_group_info
  • zabbix_host_facts module - removed in favour of zabbix_host_info

hetzner.hcloud

  • inventory plugin - Python v3.5+ is now required.

lowlydba.sqlserver

  • Updating minimum DBATools version to v2.0.0 to allow for pwsh 7.3+ compatibility. There may also be breaking change behavior in DBATools, see https://blog.netnerds.net/2023/03/whats-new-dbatools-2.0/. (https://github.com/lowlydba/lowlydba.sqlserver/pull/181)

Major Changes

Ansible-core

  • ansible-test - Docker Desktop on WSL2 is now supported (additional configuration required).
  • ansible-test - Docker and Podman are now supported on hosts with cgroup v2 unified. Previously only cgroup v1 and cgroup v2 hybrid were supported.
  • ansible-test - Podman now works on container hosts without systemd. Previously only some containers worked, while others required rootfull or rootless Podman, but would not work with both. Some containers did not work at all.
  • ansible-test - Podman on WSL2 is now supported.
  • ansible-test - When additional cgroup setup is required on the container host, this will be automatically detected. Instructions on how to configure the host will be provided in the error message shown.

ansible.windows

  • Set the minimum Ansible version supported by this collection to Ansible 2.12

chocolatey.chocolatey

  • win_chocolatey - Allow users to select the TLS versions used for bootstrapping Chocolatey installation.

cisco.iosxr

  • iosxr_l3_interfaces - fix issue in ipv4 address formatting. (https://github.com/ansible-collections/cisco.iosxr/issues/311).

cisco.meraki

  • meraki_mr_l7_firewall - New module
  • meraki_webhook_payload_template - New module

community.hrobot

  • firewall - Hetzner added output rules support to the firewall. This change unfortunately means that using old versions of the firewall module will always set the output rule list to empty, thus disallowing the server to send out packets (https://github.com/ansible-collections/community.hrobot/issues/75, https://github.com/ansible-collections/community.hrobot/pull/76).

community.postgresql

  • postgresql_privs - the password argument is deprecated and will be removed in community.postgresql 4.0.0, use the login_password argument instead (https://github.com/ansible-collections/community.postgresql/issues/406).

community.vmware

  • Use true/false (lowercase) for boolean values in documentation and examples (https://github.com/ansible-collections/community.vmware/issues/1660).

community.zabbix

  • all modules are opting away from zabbix-api and using httpapi ansible.netcommon plugin. We will support zabbix-api for backwards compatibility until next major release. See our README.md for more information about how to migrate
  • zabbix_agent and zabbix_proxy roles are opting away from zabbix-api and use httpapi ansible.netcommon plugin. We will support zabbix-api for backwards compatibility until next major release. See our README.md for more information about how to migrate

containers.podman

  • New become plugin - podman_unshare
  • Podman generate systemd module

dellemc.openmanage

  • Rebranded from Dell EMC to Dell.
  • Support for IPv6 address for OMSDK dependent iDRAC modules.
  • idrac_firmware - This module is enhanced to support proxy.
  • idrac_redfish_storage_controller - This module is enhanced to configure controller attributes and online capacity expansion.
  • idrac_server_config_profile - This module is enhanced to support proxy settings, import buffer, include in export, and ignore certificate warning.
  • idrac_user_info - This module allows to retrieve iDRAC Local user information details.
  • ome_domian_user_groups - This module allows to import the LDAP directory groups.
  • ome_inventory - This plugin allows to create a inventory from the group on OpenManage Enterprise.
  • ome_inventory - This plugin is enhanced to support inventory retrieval of System and Plugin Groups of OpenManage Enterprise.
  • ome_profile_info - This module allows to retrieve profiles with attributes on OpenManage Enterprise or OpenManage Enterprise Modular.
  • ome_smart_fabric_info - This module retrieves the list of smart fabrics in the inventory of OpenManage Enterprise Modular.
  • ome_smart_fabric_uplink_info - This module retrieve details of fabric uplink on OpenManage Enterprise Modular.
  • ome_template_network_vlan_info - This module allows to retrieve the network configuration of a template on OpenManage Enterprise or OpenManage Enterprise Modular.

fortinet.fortios

  • Add annotations of member operation for every module.
  • Support FortiOS v7.0.6, v7.0.7, v7.0.8, v7.2.1, v7.2.2.
  • Update fortios.py for higher performance;
  • supports temporary session key and pre/post login banner;
  • update the examples on how to use member operation in Q&A.

infoblox.nios_modules

  • Added Grid Master Candidate feature #152
  • Added Member Assignment to network and ranges #152
  • Added NIOS Range module with Create, Update and Delete features #152
  • Fixes issue unable to update/delete EAs using Ansible plugin #180
  • Fixes static and dynamic allocation of IPV4 address of A Record #182
  • Fixes to Update host name of NIOS member #176
  • Updates default WAPI version to 2.9 #176

junipernetworks.junos

  • change gathered key from junos_acls to acls

kubernetes.core

  • refactor K8sAnsibleMixin into module_utils/k8s/ (https://github.com/ansible-collections/kubernetes.core/pull/481).

purestorage.fusion

  • Patching of resource properties was brought to parity with underlying Python SDK
  • fusion_volume - fixed and reorganized, arguments changed

Removed Collections

  • dellemc.os10 (previously included version: 1.1.1)
  • dellemc.os6 (previously included version: 1.0.7)
  • dellemc.os9 (previously included version: 1.0.4)
  • mellanox.onyx (previously included version: 1.0.0)

Removed Features

  • dellemc.os10 was considered unmaintained and removed from Ansible 8 as per the removal from Ansible process. Users can still install this collection with ansible-galaxy collection install dellemc.os10.
  • dellemc.os6 was considered unmaintained and removed from Ansible 8 as per the removal from Ansible process. Users can still install this collection with ansible-galaxy collection install dellemc.os6.
  • dellemc.os9 was considered unmaintained and removed from Ansible 8 as per the removal from Ansible process. Users can still install this collection with ansible-galaxy collection install dellemc.os9.
  • mellanox.onyx was considered unmaintained and removed from Ansible 8 as per the removal from Ansible process. Users can still install this collection with ansible-galaxy collection install mellanox.onyx.

Ansible-core

  • Remove deprecated ANSIBLE_CALLBACK_WHITELIST configuration environment variable, use ANSIBLE_CALLBACKS_ENABLED instead. (https://github.com/ansible/ansible/issues/78821)
  • Remove deprecated ANSIBLE_COW_WHITELIST configuration environment variable, use ANSIBLE_COW_ACCEPTLIST instead. (https://github.com/ansible/ansible/issues/78819)
  • Remove deprecated callback_whitelist configuration option, use callbacks_enabled instead. (https://github.com/ansible/ansible/issues/78822)
  • Remove deprecated cow_whitelist configuration option, use cowsay_enabled_stencils instead. (https://github.com/ansible/ansible/issues/78820)

amazon.aws

  • ec2_vpc_endpoint_info - support for the query parameter was removed. The amazon.aws.ec2_vpc_endpoint_info module now only queries for endpoints. Services can be queried using the amazon.aws.ec2_vpc_endpoint_service_info module (https://github.com/ansible-collections/amazon.aws/pull/1308).
  • s3_object - support for creating and deleting buckets using the s3_object module has been removed. S3 buckets can be created and deleted using the amazon.aws.s3_bucket module (https://github.com/ansible-collections/amazon.aws/issues/1112).

ansible.netcommon

  • cli_parse - This plugin was moved to ansible.utils in version 1.0.0, and the redirect to that collection has now been removed.

community.general

  • All sap modules have been removed from this collection. They have been migrated to the community.sap_libs collection. Redirections have been provided. Following modules are affected: - sapcar_extract - sap_task_list_execute - hana_query
  • cmd_runner module utils - the fmt alias of cmd_runner_fmt has been removed. Use cmd_runner_fmt instead (https://github.com/ansible-collections/community.general/pull/6428).
  • newrelic_deployment - the appname and environment options have been removed. They did not do anything (https://github.com/ansible-collections/community.general/pull/6428).
  • puppet - the alias show-diff of the show_diff option has been removed. Use show_diff instead (https://github.com/ansible-collections/community.general/pull/6428).
  • xfconf - generating facts was deprecated in community.general 3.0.0, however three factoids, property, channel and value continued to be generated by mistake. This behaviour has been removed and xfconf generate no facts whatsoever (https://github.com/ansible-collections/community.general/pull/5502).
  • xfconf - generating facts was deprecated in community.general 3.0.0, however two factoids, previous_value and type continued to be generated by mistake. This behaviour has been removed and xfconf generate no facts whatsoever (https://github.com/ansible-collections/community.general/pull/5502).

community.zabbix

  • agent role - removed support to configure firewall
  • web role - removed installation of apache, debian, and php

Deprecated Features

  • The cisco.nso collection is considered unmaintained and will be removed from Ansible 9 if no one starts maintaining it again before Ansible 9. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/155).
  • The community.fortios collection is considered unmaintained and will be removed from Ansible 9 if no one starts maintaining it again before Ansible 9. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/162).
  • The community.google collection is considered unmaintained and will be removed from Ansible 9 if no one starts maintaining it again before Ansible 9. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/160).
  • The community.skydive collection is considered unmaintained and will be removed from Ansible 9 if no one starts maintaining it again before Ansible 9. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/171).
  • The netapp.aws collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works (https://github.com/ansible-community/community-topics/issues/223).

Ansible-core

  • The ConnectionBase()._new_stdin attribute is deprecated, use display.prompt_until(msg) instead.
  • ansible-test - The foreman test plugin is now deprecated. It will be removed in a future release.
  • ansible-test - The govcsim simulator in the vcenter test plugin is now deprecated. It will be removed in a future release. Users should switch to providing their own test environment through a static configuration file.
  • password_hash - deprecate using passlib.hash.hashtype if hashtype isn’t in the list of documented choices.
  • vars - Specifying a list of dictionaries for vars: is deprecated in favor of specifying a dictionary.

amazon.aws

  • amazon.aws collection - due to the AWS SDKs Python support policies (https://aws.amazon.com/blogs/developer/python-support-policy-updates-for-aws-sdks-and-tools/) support for Python less than 3.8 by this collection is expected to be removed in a release after 2024-12-01 (https://github.com/ansible-collections/amazon.aws/pull/1342).
  • amazon.aws collection - due to the AWS SDKs announcing the end of support for Python less than 3.7 (https://aws.amazon.com/blogs/developer/python-support-policy-updates-for-aws-sdks-and-tools/) support for Python less than 3.7 by this collection has been deprecated and will be removed in release 7.0.0. (https://github.com/ansible-collections/amazon.aws/pull/1342).
  • amazon.aws lookup plugins - the boto3_profile alias for the profile option has been deprecated, please use profile instead (https://github.com/ansible-collections/amazon.aws/pull/1225).
  • docs_fragments - amazon.aws.aws_credentials docs fragment has been deprecated please use amazon.aws.common.plugins instead (https://github.com/ansible-collections/amazon.aws/pull/1248).
  • docs_fragments - amazon.aws.aws_region docs fragment has been deprecated please use amazon.aws.region.plugins instead (https://github.com/ansible-collections/amazon.aws/pull/1248).
  • docs_fragments - amazon.aws.aws docs fragment has been deprecated please use amazon.aws.common.modules instead (https://github.com/ansible-collections/amazon.aws/pull/1248).
  • docs_fragments - amazon.aws.ec2 docs fragment has been deprecated please use amazon.aws.region.modules instead (https://github.com/ansible-collections/amazon.aws/pull/1248).
  • module_utils.policy - ansible_collections.amazon.aws.module_utils.policy.sort_json_policy_dict has been deprecated consider using ansible_collections.amazon.aws.module_utils.poilcies.compare_policies instead (https://github.com/ansible-collections/amazon.aws/pull/1136).
  • s3_object - Support for passing dualstack and endpoint_url at the same time has been deprecated, the dualstack parameter is ignored when endpoint_url is passed. Support will be removed in a release after 2024-12-01 (https://github.com/ansible-collections/amazon.aws/pull/1305).
  • s3_object - Support for passing values of overwrite other than always, never, different or last last has been deprecated. Boolean values should be replaced by the strings always or never Support will be removed in a release after 2024-12-01 (https://github.com/ansible-collections/amazon.aws/pull/1305).
  • s3_object_info - Support for passing dualstack and endpoint_url at the same time has been deprecated, the dualstack parameter is ignored when endpoint_url is passed. Support will be removed in a release after 2024-12-01 (https://github.com/ansible-collections/amazon.aws/pull/1305).
  • support for passing both profile and security tokens through a mix of environment variables and parameters has been deprecated and support will be removed in release 6.0.0. After release 6.0.0 it will only be possible to pass either a profile or security tokens, regardless of mechanism used to pass them. To explicitly block a parameter coming from an environment variable pass an empty string as the parameter value. Support for passing profile and security tokens together was originally deprecated in release 1.2.0, however only partially implemented in release 5.0.0 (https://github.com/ansible-collections/amazon.aws/pull/1355).

check_point.mgmt

  • add/set/delete nat-rule modules - will be replaced by the single cp_mgmt_nat_rule module.
  • cp_mgmt_show_task/s modules - will be replaced by the by the single cp_mgmt_task_facts module.

chocolatey.chocolatey

  • win_chocolatey - Deprecate side-by-side installs.

cisco.ios

  • ios_bgp_address_family - deprecate neighbors.address/tag/ipv6_adddress with neighbor_address which enables common attributes for facts rendering
  • ios_bgp_address_family - deprecate neighbors.password with password_options which allows encryption and password
  • ios_bgp_address_family - deprecate redistribute.ospf.match.external with redistribute.ospf.match.externals which enables attributes for OSPF type E1 and E2 routes
  • ios_bgp_address_family - deprecate redistribute.ospf.match.nssa_external with redistribute.ospf.match.nssa_externals which enables attributes for OSPF type N1 and N2 routes
  • ios_bgp_address_family - deprecate redistribute.ospf.match.type_1 with redistribute.ospf.match.nssa_externals.type_1
  • ios_bgp_address_family - deprecate redistribute.ospf.match.type_2 with redistribute.ospf.match.nssa_externals.type_2
  • ios_bgp_address_family - deprecate slow_peer with slow_peer_options which supports a dict attribute

community.aws

  • community.aws collection - due to the AWS SDKs Python support policies (https://aws.amazon.com/blogs/developer/python-support-policy-updates-for-aws-sdks-and-tools/) support for Python less than 3.8 by this collection is expected to be removed in a release after 2024-12-01 (https://github.com/ansible-collections/community.aws/pull/1743).
  • community.aws collection - due to the AWS SDKs announcing the end of support for Python less than 3.7 (https://aws.amazon.com/blogs/developer/python-support-policy-updates-for-aws-sdks-and-tools/) support for Python less than 3.7 by this collection has been deprecated and will be removed in release 7.0.0. (https://github.com/ansible-collections/community.aws/pull/1743).
  • ecs_service - In a release after 2024-06-01, tha default value of purge_placement_constraints will be change from false to true (https://github.com/ansible-collections/community.aws/pull/1716).
  • ecs_service - In a release after 2024-06-01, tha default value of purge_placement_strategy will be change from false to true (https://github.com/ansible-collections/community.aws/pull/1716).
  • iam_role - All top level return values other than iam_role and changed have been deprecated and will be removed in a release after 2023-12-01 (https://github.com/ansible-collections/community.aws/issues/551).
  • iam_role - In a release after 2023-12-01 the contents of assume_role_policy_document will no longer be converted from CamelCase to snake_case. The assume_role_policy_document_raw return value already returns the policy document in this future format (https://github.com/ansible-collections/community.aws/issues/551).
  • iam_role_info - In a release after 2023-12-01 the contents of assume_role_policy_document will no longer be converted from CamelCase to snake_case. The assume_role_policy_document_raw return value already returns the policy document in this future format (https://github.com/ansible-collections/community.aws/issues/551).

community.crypto

  • x509_crl - the mode option is deprecated; use crl_mode instead. The mode option will change its meaning in community.crypto 3.0.0, and will refer to the CRL file’s mode instead (https://github.com/ansible-collections/community.crypto/issues/596).

community.dns

  • The default of the newly added option txt_character_encoding will change from octal to decimal in community.dns 3.0.0. The new default will be compatible with RFC 1035 (https://github.com/ansible-collections/community.dns/pull/134).

community.general

  • ModuleHelper module_utils - deps mixin for MH classes deprecated in favour of using the deps module_utils (https://github.com/ansible-collections/community.general/pull/6465).
  • consul - deprecate using parameters unused for state=absent (https://github.com/ansible-collections/community.general/pull/5772).
  • gitlab_runner - the default of the new option access_level_on_creation will change from false to true in community.general 7.0.0. This will cause access_level to be used during runner registration as well, and not only during updates (https://github.com/ansible-collections/community.general/pull/5908).
  • gitlab_runner - the option access_level will lose its default value in community.general 8.0.0. From that version on, you have set this option to ref_protected explicitly, if you want to have a protected runner (https://github.com/ansible-collections/community.general/issues/5925).
  • manageiq_policies - deprecate state=list in favour of using community.general.manageiq_policies_info (https://github.com/ansible-collections/community.general/pull/5721).
  • manageiq_tags - deprecate state=list in favour of using community.general.manageiq_tags_info (https://github.com/ansible-collections/community.general/pull/5727).
  • rax - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax module utils - module utils code relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_cbs - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_cbs_attachments - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_cdb - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_cdb_database - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_cdb_user - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_clb - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_clb_nodes - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_clb_ssl - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_dns - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_dns_record - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_facts - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_files - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_files_objects - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_identity - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_keypair - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_meta - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_mon_alarm - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_mon_check - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_mon_entity - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_mon_notification - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_mon_notification_plan - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_network - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_queue - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_scaling_group - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rax_scaling_policy - module relies on deprecated library pyrax and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/5752).
  • rhn_channel, rhn_register - RHN hosted at redhat.com was discontinued years ago, and Spacewalk 5 (which uses RHN) is EOL since 2020, May 31st; while these modules could work on Uyuni / SUSE Manager (fork of Spacewalk 5), we have not heard about anyone using them in those setups. Hence, these modules are deprecated, and will be removed in community.general 10.0.0 in case there are no reports about being still useful, and potentially no one that steps up to maintain them (https://github.com/ansible-collections/community.general/pull/6493).

community.hashi_vault

  • ansible-core - support for ansible-core versions 2.11 and 2.12 will be dropped in collection version 5.0.0, making 2.13 the minimum supported version of ansible-core (https://github.com/ansible-collections/community.hashi_vault/issues/340).
  • hashi_vault lookup - in v5.0.0 duplicate term string options will raise an exception instead of showing a warning (https://github.com/ansible-collections/community.hashi_vault/issues/356).
  • hvac - the minimum version of hvac to be supported in collection version 5.0.0 will be at least 1.0.2; this minimum may be raised before 5.0.0 is released, so please subscribe to the linked issue and look out for new notices in the changelog (https://github.com/ansible-collections/community.hashi_vault/issues/324).

purestorage.fusion

  • fusion_hw - hardware module is being removed as changing hardware type has never been supported by Pure Storage Fusion
  • fusion_info - nigs subset is deprecated in favor of network_interface_groups and will be removed in the version 1.7.0
  • fusion_info - placements subset is deprecated in favor of placement_groups and will be removed in the version 1.7.0
  • fusion_pg - placement_engine option is deprecated because Fusion API does not longer support this parameter It will be removed in the version 2.0.0
  • fusion_se - parameters ‘addresses’, ‘gateway’ and ‘network_interface_groups’ are deprecated in favor of ‘iscsi’ and will be removed in version 2.0.0
  • fusion_tn - tenant networks are being replaced by storage endpoints `fusion_se` and Network Interface Groups `fusion_nig`

© 2012–2018 Michael DeHaan
© 2018–2025 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/projects/ansible/latest/porting_guides/porting_guide_8.html

Spec-Zone.ru

Настройки Оффлайн Что нового Помощь О нас
Spec-Zone .ru
спецификации, руководства, описания, API