"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/docsite/rst/porting_guides/porting_guide_7.rst" between
ansible-2.14.0.tar.gz and ansible-2.14.1rc1.tar.gz

About: Ansible is an IT Configuration Management, Deployment & Orchestration tool.
Release candidate.

porting_guide_7.rst  (ansible-2.14.0):porting_guide_7.rst  (ansible-2.14.1rc1)
skipping to change at line 83 skipping to change at line 83
Porting custom scripts Porting custom scripts
====================== ======================
No notable changes No notable changes
Networking Networking
========== ==========
No notable changes No notable changes
Porting Guide for v7.0.0a2 Porting Guide for v7.0.0
========================== ========================
Added Collections Added Collections
----------------- -----------------
- lowlydba.sqlserver (version 1.0.3) - ibm.spectrum_virtualize (version 1.10.0)
- inspur.ispim (version 1.2.0)
- lowlydba.sqlserver (version 1.0.4)
- purestorage.fusion (version 1.1.1)
- vultr.cloud (version 1.3.1)
Known Issues Known Issues
------------ ------------
community.routeros
~~~~~~~~~~~~~~~~~~
- The ``community.routeros.command`` module claims to support check mode. Since
it cannot judge whether the commands executed modify state or not, this behavior
is incorrect. Since this potentially breaks existing playbooks, we will not cha
nge this behavior until community.routeros 3.0.0.
dellemc.openmanage dellemc.openmanage
~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~
- 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 ch anges 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 ch anges or a configuration job is in progress``. Wait for the job to complete and run the task again.
- ome_application_alerts_smtp - Issue(212310) - The module does not provide a pr oper error message if the destination_address is more than 255 characters.
- 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_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_local_access_configuration - Issue(215035) - The module reports ``S
uccessfully updated the local access setting`` if an unsupported value is provid
ed for the parameter timeout_limit. However, this value is not actually applied
on OpenManage Enterprise Modular.
- ome_device_local_access_configuration - Issue(217865) - The module does not di
splay a proper error message if an unsupported value is provided for the user_de
fined and lcd_language parameters.
- ome_device_network_services - Issue(212681) - The module does not provide a pr oper error message if unsupported values are provided for the parameters- port_n umber, community_name, max_sessions, max_auth_retries, and idle_timeout. - ome_device_network_services - Issue(212681) - The module does not provide a pr oper error message if unsupported values are provided for the parameters- port_n umber, 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_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_device_quick_deploy - Issue(216352) - The module does not display a proper error message if an unsupported value is provided for the ipv6_prefix_length an d vlan_id parameters.
- ome_smart_fabric_uplink - Issue(186024) - The module does not allow the creati on of multiple uplinks of the same name even though it is supported by OpenManag e Enterprise Modular. 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 creati on of multiple uplinks of the same name even though it is supported by OpenManag e Enterprise Modular. If an uplink is created using the same name as an existing uplink, the existing uplink is modified.
netapp.ontap
~~~~~~~~~~~~
- na_ontap_snapshot - added documentation to use UTC format for ``expiry_time``.
Breaking Changes Breaking Changes
---------------- ----------------
- Ansible 7 requires Python 3.9 on the controller, same as ansible-core 2.14.
Ansible-core Ansible-core
~~~~~~~~~~~~ ~~~~~~~~~~~~
- Allow for lazy evaluation of Jinja2 expressions (https://github.com/ansible/an
sible/issues/56017)
- The default ansible-galaxy role skeletons no longer contain .travis.yml files.
You can configure ansible-galaxy to use a custom role skeleton that contains a
.travis.yml file to continue using Galaxy's integration with Travis CI.
- ansible - At startup the filesystem encoding and locale are checked to verify
they are UTF-8. If not, the process exits with an error reporting the errant enc
oding.
- ansible - Increase minimum Python requirement to Python 3.9 for CLI utilities
and controller code
- ansible-test - At startup the filesystem encoding is checked to verify it is U
TF-8. If not, the process exits with an error reporting the errant encoding.
- ansible-test - At startup the locale is configured as ``en_US.UTF-8``, with a
fallback to ``C.UTF-8``. If neither encoding is available the process exits with
an error. If the fallback is used, a warning is displayed. In previous versions
the ``en_US.UTF-8`` locale was always requested. However, no startup checking w
as performed to verify the locale was successfully configured.
- ansible-test validate-modules - Removed the ``missing-python-doc`` error code in validate modules, ``missing-documentation`` is used instead for missing Power Shell module documentation. - ansible-test validate-modules - Removed the ``missing-python-doc`` error code in validate modules, ``missing-documentation`` is used instead for missing Power Shell module documentation.
- strategy plugins - Make ``ignore_unreachable`` to increase ``ignored`` and ``o k`` and counter, not ``skipped`` and ``unreachable``. (https://github.com/ansib le/ansible/issues/77690)
amazon.aws amazon.aws
~~~~~~~~~~ ~~~~~~~~~~
- Tags beginning with ``aws:`` will not be removed when purging tags, these tags are reserved by Amazon and may not be updated or deleted (https://github.com/an sible-collections/amazon.aws/issues/817).
- amazon.aws collection - Support for ansible-core < 2.11 has been dropped (http s://github.com/ansible-collections/amazon.aws/pull/1087). - amazon.aws collection - Support for ansible-core < 2.11 has been dropped (http s://github.com/ansible-collections/amazon.aws/pull/1087).
- amazon.aws collection - The amazon.aws collection has dropped support for ``bo tocore<1.21.0`` and ``boto3<1.18.0``. Most modules will continue to work with ol der versions of the AWS SDK, however compatability with older versions of the SD K 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/am azon.aws/pull/934). - amazon.aws collection - The amazon.aws collection has dropped support for ``bo tocore<1.21.0`` and ``boto3<1.18.0``. Most modules will continue to work with ol der versions of the AWS SDK, however compatability with older versions of the SD K 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/am azon.aws/pull/934).
- amazon.aws collection - the ``profile`` parameter is now mutually exclusive wi
th the ``aws_access_key``, ``aws_secret_key`` and ``security_token`` parameters
(https://github.com/ansible-collections/amazon.aws/pull/834).
- aws_az_info - the module alias ``aws_az_facts`` was deprecated in Ansible 2.9
and has now been removed (https://github.com/ansible-collections/amazon.aws/pull
/832).
- aws_s3 - the default value for ``ensure overwrite`` has been changed to ``diff
erent`` instead of ``always`` so that the module is idempotent by default (https
://github.com/ansible-collections/amazon.aws/issues/811).
- aws_ssm - on_denied and on_missing now both default to error, for consistency
with both aws_secret and the base Lookup class (https://github.com/ansible-colle
ctions/amazon.aws/issues/617).
- doc_fragments - remove minimum collection requirements from doc_fragments/aws. py and allow pulling those from doc_fragments/aws_boto3.py instead (https://gith ub.com/ansible-collections/amazon.aws/pull/985). - doc_fragments - remove minimum collection requirements from doc_fragments/aws. py and allow pulling those from doc_fragments/aws_boto3.py instead (https://gith ub.com/ansible-collections/amazon.aws/pull/985).
- ec2 - The ``ec2`` module has been removed in release 4.0.0 and replaced by the ``ec2_instance`` module (https://github.com/ansible-collections/amazon.aws/pull /630).
- ec2_ami - the default value for ``purge_tags`` has been changed from ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916). - ec2_ami - the default value for ``purge_tags`` has been changed from ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916).
- ec2_ami - the parameter aliases ``DeviceName``, ``VirtualName`` and ``NoDevice `` were previously deprecated and have been removed, please use ``device_name``, ``virtual_name`` and ``no_device`` instead (https://github.com/ansible-collecti ons/amazon.aws/pull/913). - ec2_ami - the parameter aliases ``DeviceName``, ``VirtualName`` and ``NoDevice `` were previously deprecated and have been removed, please use ``device_name``, ``virtual_name`` and ``no_device`` instead (https://github.com/ansible-collecti ons/amazon.aws/pull/913).
- ec2_eni_info - the mutual exclusivity of the ``eni_id`` and ``filters`` parame ters is now enforced, previously ``filters`` would be ignored if ``eni_id`` was set (https://github.com/ansible-collections/amazon.aws/pull/954). - ec2_eni_info - the mutual exclusivity of the ``eni_id`` and ``filters`` parame ters is now enforced, previously ``filters`` would be ignored if ``eni_id`` was set (https://github.com/ansible-collections/amazon.aws/pull/954).
- ec2_instance - the default value for ``purge_tags`` has been changed from ``Fa lse`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916). - ec2_instance - the default value for ``purge_tags`` has been changed from ``Fa lse`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916).
- ec2_key - the default value for ``purge_tags`` has been changed from ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916). - ec2_key - the default value for ``purge_tags`` has been changed from ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916).
- ec2_vol - the default value for ``purge_tags`` has been changed from ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916). - ec2_vol - the default value for ``purge_tags`` has been changed from ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916).
- ec2_vpc_dhcp_option_info - the parameter aliases ``DhcpOptionIds`` and ``DryRu n`` were previously deprecated and have been removed, please use ``dhcp_options_ ids`` and ``no_device`` instead (https://github.com/ansible-collections/amazon.a ws/pull/913). - ec2_vpc_dhcp_option_info - the parameter aliases ``DhcpOptionIds`` and ``DryRu n`` were previously deprecated and have been removed, please use ``dhcp_options_ ids`` and ``no_device`` instead (https://github.com/ansible-collections/amazon.a ws/pull/913).
- ec2_vpc_endpoint - the default value for ``purge_tags`` has been changed from ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/91 6). - ec2_vpc_endpoint - the default value for ``purge_tags`` has been changed from ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/91 6).
- ec2_vpc_igw_info - The default value for ``convert_tags`` has been changed to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/835).
- ec2_vpc_net - the default value for ``purge_tags`` has been changed from ``Fal se`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916). - ec2_vpc_net - the default value for ``purge_tags`` has been changed from ``Fal se`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull/916).
- ec2_vpc_route_table - the default value for ``purge_tags`` has been changed fr om ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull /916). - ec2_vpc_route_table - the default value for ``purge_tags`` has been changed fr om ``False`` to ``True`` (https://github.com/ansible-collections/amazon.aws/pull /916).
- elb_classic_lb - the ``ec2_elb`` fact has been removed (https://github.com/ans
ible-collections/amazon.aws/pull/827).
- module_utils - Support for the original AWS SDK aka ``boto`` has been removed,
including all relevant helper functions. All modules should now use the ``boto3
``/``botocore`` AWS SDK (https://github.com/ansible-collections/amazon.aws/pull/
630)
- s3_bucket - the previously deprecated alias ``S3_URL`` for the ``s3_url`` para meter has been removed. Playbooks shuold be updated to use ``s3_url`` (https:// github.com/ansible-collections/amazon.aws/pull/908). - s3_bucket - the previously deprecated alias ``S3_URL`` for the ``s3_url`` para meter has been removed. Playbooks shuold be updated to use ``s3_url`` (https:// github.com/ansible-collections/amazon.aws/pull/908).
- s3_object - the previously deprecated alias ``S3_URL`` for the ``s3_url`` para meter has been removed. Playbooks should be updated to use ``s3_url`` (https:// github.com/ansible-collections/amazon.aws/pull/908). - s3_object - the previously deprecated alias ``S3_URL`` for the ``s3_url`` para meter has been removed. Playbooks should be updated to use ``s3_url`` (https:// github.com/ansible-collections/amazon.aws/pull/908).
check_point.mgmt
~~~~~~~~~~~~~~~~
- cp_mgmt_access_role - the 'machines' parameter now accepts a single str and a
new parameter 'machines_list' of type dict has been added. the 'users' parameter
now accepts a single str and a new parameter 'users_list' of type dict has been
added.
- cp_mgmt_access_rule - the 'vpn' parameter now accepts a single str and a new p
arameter 'vpn_list' of type dict has been added. the 'position_by_rule' paramete
r has been changed to 'relative_position' with support of positioning above/belo
w a section (and not just a rule). the 'relative_position' parameter has also 't
op' and 'bottom' suboptions which allows positioning a rule at the top and botto
m of a section respectively. a new parameter 'search_entire_rulebase' has been a
dded to allow the relative positioning to be unlimited (was previously limited t
o 50 rules)
- cp_mgmt_administrator - the 'permissions_profile' parameter now accepts a sing
le str and a new parameter 'permissions_profile_list' of type dict has been adde
d.
- cp_mgmt_publish - the 'uid' parameter has been removed.
community.aws community.aws
~~~~~~~~~~~~~ ~~~~~~~~~~~~~
- Tags beginning with ``aws:`` will not be removed when purging tags, these tags are reserved by Amazon and may not be updated or deleted (https://github.com/an sible-collections/amazon.aws/issues/817).
- acm_certificate - the previously deprecated default value of ``purge_tags=Fals e`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collecti ons/community.aws/pull/1343). - acm_certificate - the previously deprecated default value of ``purge_tags=Fals e`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collecti ons/community.aws/pull/1343).
- autoscaling_group - The module has been migrated from the ``community.aws`` co llection. Playbooks using the Fully Qualified Collection Name for this module sh ould be updated to use ``amazon.aws.autoscaling_group``. - autoscaling_group - The module has been migrated from the ``community.aws`` co llection. Playbooks using the Fully Qualified Collection Name for this module sh ould be updated to use ``amazon.aws.autoscaling_group``.
- autoscaling_group_info - The module has been migrated from the ``community.aws `` collection. Playbooks using the Fully Qualified Collection Name for this modu le should be updated to use ``amazon.aws.autoscaling_group_info``. - autoscaling_group_info - The module has been migrated from the ``community.aws `` collection. Playbooks using the Fully Qualified Collection Name for this modu le should be updated to use ``amazon.aws.autoscaling_group_info``.
- aws_secret - tags are no longer removed when the ``tags`` parameter is not set . To remove all tags set ``tags={}`` (https://github.com/ansible-collections/co mmunity.aws/issues/1146).
- cloudfront_distribution - the previously deprecated default value of ``purge_t ags=False`` has been updated to ``purge_tags=True`` (https://github.com/ansible- collections/community.aws/pull/1343). - cloudfront_distribution - the previously deprecated default value of ``purge_t ags=False`` has been updated to ``purge_tags=True`` (https://github.com/ansible- collections/community.aws/pull/1343).
- cloudtrail - The module has been migrated to the ``amazon.aws`` collection. Pl aybooks using the Fully Qualified Collection Name for this module should be upda ted to use ``amazon.aws.cloudtrail``. - cloudtrail - The module has been migrated to the ``amazon.aws`` collection. Pl aybooks using the Fully Qualified Collection Name for this module should be upda ted to use ``amazon.aws.cloudtrail``.
- cloudwatch_metric_alarm - The module has been migrated from the ``community.aw s`` collection. Playbooks using the Fully Qualified Collection Name for this mod ule should be updated to use ``amazon.aws.cloudwatch_metric_alarm``. - cloudwatch_metric_alarm - The module has been migrated from the ``community.aw s`` collection. Playbooks using the Fully Qualified Collection Name for this mod ule should be updated to use ``amazon.aws.cloudwatch_metric_alarm``.
- cloudwatchevent_rule - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.cloudwatchevent_rule``. - cloudwatchevent_rule - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.cloudwatchevent_rule``.
- cloudwatchlogs_log_group - The module has been migrated from the ``community.a ws`` collection. Playbooks using the Fully Qualified Collection Name for this mo dule should be updated to use ``amazon.aws.cloudwatchlogs_log_group``. - cloudwatchlogs_log_group - The module has been migrated from the ``community.a ws`` collection. Playbooks using the Fully Qualified Collection Name for this mo dule should be updated to use ``amazon.aws.cloudwatchlogs_log_group``.
- cloudwatchlogs_log_group_info - The module has been migrated from the ``commun ity.aws`` collection. Playbooks using the Fully Qualified Collection Name for th is module should be updated to use ``amazon.aws.cloudwatchlogs_log_group_info``. - cloudwatchlogs_log_group_info - The module has been migrated from the ``commun ity.aws`` collection. Playbooks using the Fully Qualified Collection Name for th is module should be updated to use ``amazon.aws.cloudwatchlogs_log_group_info``.
- cloudwatchlogs_log_group_metric_filter - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Na me for this module should be updated to use ``amazon.aws.cloudwatchlogs_log_grou p_metric_filter``. - cloudwatchlogs_log_group_metric_filter - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Na me for this module should be updated to use ``amazon.aws.cloudwatchlogs_log_grou p_metric_filter``.
- community.aws collection - Support for ansible-core < 2.11 has been dropped (h ttps://github.com/ansible-collections/community.aws/pull/1541). - community.aws collection - Support for ansible-core < 2.11 has been dropped (h ttps://github.com/ansible-collections/community.aws/pull/1541).
- community.aws collection - The ``community.aws`` collection has now dropped su pport for and any requirements upon the original ``boto`` AWS SDK, and now uses the ``boto3``/``botocore`` AWS SDK (https://github.com/ansible-collections/commu nity.aws/pull/898).
- community.aws collection - The community.aws collection has dropped support fo r ``botocore<1.21.0`` and ``boto3<1.18.0``. Most modules will continue to work w ith 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 t he SDK a warning will be emitted by Ansible (https://github.com/ansible-collecti ons/community.aws/pull/1362). - community.aws collection - The community.aws collection has dropped support fo r ``botocore<1.21.0`` and ``boto3<1.18.0``. Most modules will continue to work w ith 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 t he SDK a warning will be emitted by Ansible (https://github.com/ansible-collecti ons/community.aws/pull/1362).
- community.aws collection - the ``profile`` parameter is now mutually exclusive with the ``aws_access_key``, ``aws_secret_key`` and ``security_token`` paramete rs (https://github.com/ansible-collections/amazon.aws/pull/834).
- ec2_eip - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be up dated to use ``amazon.aws.ec2_eip``. - ec2_eip - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be up dated to use ``amazon.aws.ec2_eip``.
- ec2_eip_info - The module has been migrated from the ``community.aws`` collect ion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.ec2_eip_info``. - ec2_eip_info - The module has been migrated from the ``community.aws`` collect ion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.ec2_eip_info``.
- ec2_vpc_route_table - The module has been migrated from the ``community.aws``
collection. Playbooks using the Fully Qualified Collection Name for this module
should be updated to use ``amazon.aws.ec2_vpc_route_table``.
- ec2_vpc_route_table_info - The module has been migrated from the ``community.a
ws`` collection. Playbooks using the Fully Qualified Collection Name for this mo
dule should be updated to use ``amazon.aws.ec2_vpc_route_table_info``.
- ec2_vpc_vpn - the previously deprecated default value of ``purge_tags=False`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collections/ community.aws/pull/1343). - ec2_vpc_vpn - the previously deprecated default value of ``purge_tags=False`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collections/ community.aws/pull/1343).
- elb_application_lb - The module has been migrated from the ``community.aws`` c ollection. Playbooks using the Fully Qualified Collection Name for this module s hould be updated to use ``amazon.aws.elb_application_lb``. - elb_application_lb - The module has been migrated from the ``community.aws`` c ollection. Playbooks using the Fully Qualified Collection Name for this module s hould be updated to use ``amazon.aws.elb_application_lb``.
- elb_application_lb_info - The module has been migrated from the ``community.aw s`` collection. Playbooks using the Fully Qualified Collection Name for this mod ule should be updated to use ``amazon.aws.elb_application_lb_info``. - elb_application_lb_info - The module has been migrated from the ``community.aw s`` collection. Playbooks using the Fully Qualified Collection Name for this mod ule should be updated to use ``amazon.aws.elb_application_lb_info``.
- elb_instance - the ``ec2_elbs`` fact has been removed, ``updated_elbs`` has be
en added the return values and includes the same information (https://github.com
/ansible-collections/community.aws/pull/1173).
- elb_network_lb - the default value of ``state`` has changed from ``absent`` to
``present`` (https://github.com/ansible-collections/community.aws/pull/1167).
- execute_lambda - The module has been migrated from the ``community.aws`` colle ction. Playbooks using the Fully Qualified Collection Name for this module shoul d be updated to use ``amazon.aws.execute_lambda``. - execute_lambda - The module has been migrated from the ``community.aws`` colle ction. Playbooks using the Fully Qualified Collection Name for this module shoul d be updated to use ``amazon.aws.execute_lambda``.
- iam_policy - The module has been migrated from the ``community.aws`` collectio n. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.iam_policy``. - iam_policy - The module has been migrated from the ``community.aws`` collectio n. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.iam_policy``.
- iam_policy_info - The module has been migrated from the ``community.aws`` coll ection. Playbooks using the Fully Qualified Collection Name for this module shou ld be updated to use ``amazon.aws.iam_policy_info``. - iam_policy_info - The module has been migrated from the ``community.aws`` coll ection. Playbooks using the Fully Qualified Collection Name for this module shou ld be updated to use ``amazon.aws.iam_policy_info``.
- iam_server_certificate - Passing file names to the ``cert``, ``chain_cert`` an d ``key`` parameters has been removed. We recommend using a lookup plugin to rea d the files instead, see the documentation for an example (https://github.com/an sible-collections/community.aws/pull/1265). - iam_server_certificate - Passing file names to the ``cert``, ``chain_cert`` an d ``key`` parameters has been removed. We recommend using a lookup plugin to rea d the files instead, see the documentation for an example (https://github.com/an sible-collections/community.aws/pull/1265).
- iam_server_certificate - the default value for the ``dup_ok`` parameter has be en changed to ``true``. To preserve the original behaviour explicitly set the `` dup_ok`` parameter to ``false`` (https://github.com/ansible-collections/communit y.aws/pull/1265). - iam_server_certificate - the default value for the ``dup_ok`` parameter has be en changed to ``true``. To preserve the original behaviour explicitly set the `` dup_ok`` parameter to ``false`` (https://github.com/ansible-collections/communit y.aws/pull/1265).
- iam_user - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be u pdated to use ``amazon.aws.iam_user``. - iam_user - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be u pdated to use ``amazon.aws.iam_user``.
- iam_user_info - The module has been migrated from the ``community.aws`` collec tion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.iam_user_info``. - iam_user_info - The module has been migrated from the ``community.aws`` collec tion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.iam_user_info``.
- kms_key - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be up dated to use ``amazon.aws.kms_key``. - kms_key - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be up dated to use ``amazon.aws.kms_key``.
- kms_key - managing the KMS IAM Policy via ``policy_mode`` and ``policy_grant_t ypes`` was previously deprecated and has been removed in favor of the ``policy`` option (https://github.com/ansible-collections/community.aws/pull/1344). - kms_key - managing the KMS IAM Policy via ``policy_mode`` and ``policy_grant_t ypes`` was previously deprecated and has been removed in favor of the ``policy`` option (https://github.com/ansible-collections/community.aws/pull/1344).
- kms_key - the previously deprecated default value of ``purge_tags=False`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collections/comm unity.aws/pull/1343). - kms_key - the previously deprecated default value of ``purge_tags=False`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collections/comm unity.aws/pull/1343).
skipping to change at line 185 skipping to change at line 237
- rds_param_group - The module has been migrated from the ``community.aws`` coll ection. Playbooks using the Fully Qualified Collection Name for this module shou ld be updated to use ``amazon.aws.rds_param_group``. - rds_param_group - The module has been migrated from the ``community.aws`` coll ection. Playbooks using the Fully Qualified Collection Name for this module shou ld be updated to use ``amazon.aws.rds_param_group``.
- rds_param_group - the previously deprecated default value of ``purge_tags=Fals e`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collecti ons/community.aws/pull/1343). - rds_param_group - the previously deprecated default value of ``purge_tags=Fals e`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collecti ons/community.aws/pull/1343).
- rds_snapshot_info - The module has been migrated from the ``community.aws`` co llection. Playbooks using the Fully Qualified Collection Name for this module sh ould be updated to use ``amazon.aws.rds_snapshot_info``. - rds_snapshot_info - The module has been migrated from the ``community.aws`` co llection. Playbooks using the Fully Qualified Collection Name for this module sh ould be updated to use ``amazon.aws.rds_snapshot_info``.
- rds_subnet_group - The module has been migrated from the ``community.aws`` col lection. Playbooks using the Fully Qualified Collection Name for this module sho uld be updated to use ``amazon.aws.rds_subnet_group``. - rds_subnet_group - The module has been migrated from the ``community.aws`` col lection. Playbooks using the Fully Qualified Collection Name for this module sho uld be updated to use ``amazon.aws.rds_subnet_group``.
- route53 - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be up dated to use ``amazon.aws.route53``. - route53 - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be up dated to use ``amazon.aws.route53``.
- route53_health_check - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.route53_health_check``. - route53_health_check - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.route53_health_check``.
- route53_health_check - the previously deprecated default value of ``purge_tags =False`` has been updated to ``purge_tags=True`` (https://github.com/ansible-col lections/community.aws/pull/1343). - route53_health_check - the previously deprecated default value of ``purge_tags =False`` has been updated to ``purge_tags=True`` (https://github.com/ansible-col lections/community.aws/pull/1343).
- route53_info - The module has been migrated from the ``community.aws`` collect ion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.route53_info``. - route53_info - The module has been migrated from the ``community.aws`` collect ion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.route53_info``.
- route53_zone - The module has been migrated from the ``community.aws`` collect ion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.route53_zone``. - route53_zone - The module has been migrated from the ``community.aws`` collect ion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.route53_zone``.
- route53_zone - the previously deprecated default value of ``purge_tags=False`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collections /community.aws/pull/1343). - route53_zone - the previously deprecated default value of ``purge_tags=False`` has been updated to ``purge_tags=True`` (https://github.com/ansible-collections /community.aws/pull/1343).
- script_inventory_ec2 - The ec2.py inventory script has been moved to a new rep ository. The script can now be downloaded from https://github.com/ansible-commun ity/contrib-scripts/blob/main/inventory/ec2.py and has been removed from this co llection. We recommend migrating from the script to the amazon.aws.ec2 inventory plugin. (https://github.com/ansible-collections/community.aws/pull/898)
- sqs_queue - the previously deprecated default value of ``purge_tags=False`` ha s been updated to ``purge_tags=True`` (https://github.com/ansible-collections/co mmunity.aws/pull/1343). - sqs_queue - the previously deprecated default value of ``purge_tags=False`` ha s been updated to ``purge_tags=True`` (https://github.com/ansible-collections/co mmunity.aws/pull/1343).
community.docker
~~~~~~~~~~~~~~~~
- This collection does not work with ansible-core 2.11 on Python 3.12+. Please e
ither upgrade to ansible-core 2.12+, or use Python 3.11 or earlier (https://gith
ub.com/ansible-collections/community.docker/pull/271).
- docker_container - ``exposed_ports`` is no longer ignored in ``comparisons``.
Before, its value was assumed to be identical with the value of ``published_port
s`` (https://github.com/ansible-collections/community.docker/pull/422).
- docker_container - ``log_options`` can no longer be specified when ``log_drive
r`` is not specified (https://github.com/ansible-collections/community.docker/pu
ll/422).
- docker_container - ``publish_all_ports`` is no longer ignored in ``comparisons
`` (https://github.com/ansible-collections/community.docker/pull/422).
- docker_container - ``restart_retries`` can no longer be specified when ``resta
rt_policy`` is not specified (https://github.com/ansible-collections/community.d
ocker/pull/422).
- docker_container - ``stop_timeout`` is no longer ignored for idempotency if to
ld to be not ignored in ``comparisons``. So far it defaulted to ``ignore`` there
, and setting it to ``strict`` had no effect (https://github.com/ansible-collect
ions/community.docker/pull/422).
- modules and plugins communicating directly with the Docker daemon - when conne
cting by SSH and not using ``use_ssh_client=true``, reject unknown host keys ins
tead of accepting them. This is only a breaking change relative to older communi
ty.docker 3.0.0 pre-releases or with respect to Docker SDK for Python < 6.0.0. D
ocker SDK for Python 6.0.0 will also include this change (https://github.com/ans
ible-collections/community.docker/pull/434).
community.general community.general
~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~
- newrelic_deployment - ``revision`` is required for v2 API (https://github.com/ ansible-collections/community.general/pull/5341). - newrelic_deployment - ``revision`` is required for v2 API (https://github.com/ ansible-collections/community.general/pull/5341).
- scaleway_container_registry_info - no longer replace ``secret_environment_vari
ables`` in the output by ``SENSITIVE_VALUE`` (https://github.com/ansible-collect
ions/community.general/pull/5497).
community.hashi_vault
~~~~~~~~~~~~~~~~~~~~~
- auth - the default value for ``token_validate`` has changed from ``true`` to `
`false``, as previously announced (https://github.com/ansible-collections/commun
ity.hashi_vault/issues/248).
- vault_kv2_get lookup - as previously announced, the default value for ``engine
_mount_point`` in the ``vault_kv2_get`` lookup has changed from ``kv`` to ``secr
et`` (https://github.com/ansible-collections/community.hashi_vault/issues/279).
community.vmware community.vmware
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
- Removed support for ansible-core version < 2.13.0. - Removed support for ansible-core version < 2.13.0.
- vmware_dvs_portgroup - Add a new sub-option `inherited` to the `in_traffic_sha ping` parameter. This means you can keep the setting as-is by not defining the p arameter, but also that you have to define the setting as not `inherited` if you want to override it at the PG level (https://github.com/ansible-collections/com munity.vmware/pull/1483). - vmware_dvs_portgroup - Add a new sub-option `inherited` to the `in_traffic_sha ping` parameter. This means you can keep the setting as-is by not defining the p arameter, but also that you have to define the setting as not `inherited` if you want to override it at the PG level (https://github.com/ansible-collections/com munity.vmware/pull/1483).
- vmware_dvs_portgroup - Add a new sub-option `inherited` to the `out_traffic_sh aping` parameter. This means you can keep the setting as-is by not defining the parameter, but also that you have to define the setting as not `inherited` if yo u want to override it at the PG level (https://github.com/ansible-collections/co mmunity.vmware/pull/1483). - vmware_dvs_portgroup - Add a new sub-option `inherited` to the `out_traffic_sh aping` parameter. This means you can keep the setting as-is by not defining the parameter, but also that you have to define the setting as not `inherited` if yo u want to override it at the PG level (https://github.com/ansible-collections/co mmunity.vmware/pull/1483).
- vmware_dvs_portgroup - Change the type of `net_flow` to string to allow settin g it implicitly to inherited or to keep the value as-is. This means you can keep the setting as-is by not defining the parameter, but also that while `true` or `no` still work, `True` or `Off` (uppercase) won't (https://github.com/ansible-c ollections/community.vmware/pull/1483). - vmware_dvs_portgroup - Change the type of `net_flow` to string to allow settin g it implicitly to inherited or to keep the value as-is. This means you can keep the setting as-is by not defining the parameter, but also that while `true` or `no` still work, `True` or `Off` (uppercase) won't (https://github.com/ansible-c ollections/community.vmware/pull/1483).
- vmware_dvs_portgroup - Remove support for vSphere API less than 6.7. - vmware_dvs_portgroup - Remove support for vSphere API less than 6.7.
- vmware_dvs_portgroup - Remove the default for `network_policy` and add a new s ub-option `inherited`. This means you can keep the setting as-is by not defining the parameter, but also that you have to define the setting as not `inherited` if you want to override it at the PG level (https://github.com/ansible-collectio ns/community.vmware/pull/1483). - vmware_dvs_portgroup - Remove the default for `network_policy` and add a new s ub-option `inherited`. This means you can keep the setting as-is by not defining the parameter, but also that you have to define the setting as not `inherited` if you want to override it at the PG level (https://github.com/ansible-collectio ns/community.vmware/pull/1483).
- vmware_dvs_portgroup_info - Remove support for vSphere API less than 6.7. - vmware_dvs_portgroup_info - Remove support for vSphere API less than 6.7.
- vmware_dvswitch - Remove support for vSphere API less than 6.7. - vmware_dvswitch - Remove support for vSphere API less than 6.7.
- vmware_dvswitch_uplink_pg - Remove support for vSphere API less than 6.7. - vmware_dvswitch_uplink_pg - Remove support for vSphere API less than 6.7.
- vmware_guest_boot_manager - Remove default for ``secure_boot_enabled`` paramet er (https://github.com/ansible-collections/community.vmware/issues/1461). - vmware_guest_boot_manager - Remove default for ``secure_boot_enabled`` paramet er (https://github.com/ansible-collections/community.vmware/issues/1461).
- vmware_vm_config_option - Dict item names in result are changed from strings j oined with spaces to strings joined with underlines, e.g. `Guest fullname` is ch anged to `guest_fullname` (https://github.com/ansible-collections/community.vmwa re/issues/1268). - vmware_vm_config_option - Dict item names in result are changed from strings j oined with spaces to strings joined with underlines, e.g. `Guest fullname` is ch anged to `guest_fullname` (https://github.com/ansible-collections/community.vmwa re/issues/1268).
- vmware_vspan_session - Remove support for vSphere API less than 6.7. - vmware_vspan_session - Remove support for vSphere API less than 6.7.
dellemc.enterprise_sonic
~~~~~~~~~~~~~~~~~~~~~~~~
- bgp_af - Add the route_advertise_list dictionary to the argspec to replace the
deleted, obsolete advertise_prefix attribute used for SONiC 3.x images on the 1
.x branch of this collection. This change corresponds to a SONiC 4.0 OC YANG RES
T compliance change for the BGP AF REST API. It enables specification of a route
map in conjunction with each route advertisement prefix (https://github.com/ans
ible-collections/dellemc.enterprise_sonic/pull/63).
- bgp_af - remove the obsolete 'advertise_prefix' attribute from argspec and con
fig code. This and subsequent co-req replacement with the new route advertise li
st argument structure require corresponding changes in playbooks previoulsly use
d for configuring route advertise prefixes for SONiC 3.x images. (https://github
.com/ansible-collections/dellemc.enterprise_sonic/pull/60)
- bgp_neighbors - Replace the previously defined standalone "bfd" attribute with
a bfd dictionary containing multiple attributes. This change corresponds to the
revised SONiC 4.x implementation of OC YANG compatible REST APIs. Playbooks pre
viously using the bfd attributes for SONiC 3.x images must be modified for useon
SONiC 4.0 images to use the new definition for the bfd attribute argspec struct
ure (https://github.com/ansible-collections/dellemc.enterprise_sonic/pull/72).
- bgp_neighbors - Replace, for BGP peer groups, the previously defined standalon
e "bfd" attribute with a bfd dictionary containing multiple attributes. This cha
nge corresponds to the revised SONiC 4.x implementation of OC YANG compatible RE
ST APIs. Playbooks previously using the bfd attributes for SONiC 3.x images must
be modified for useon SONiC 4.0 images to use the new definition for the bfd at
tribute argspec structure (https://github.com/ansible-collections/dellemc.enterp
rise_sonic/pull/81).
Major Changes Major Changes
------------- -------------
Ansible-core
~~~~~~~~~~~~
- Move handler processing into new ``PlayIterator`` phase to use the configured
strategy (https://github.com/ansible/ansible/issues/65067)
- ansible - At startup the filesystem encoding and locale are checked to verify
they are UTF-8. If not, the process exits with an error reporting the errant enc
oding.
- ansible - Increase minimum Python requirement to Python 3.9 for CLI utilities
and controller code
- ansible-test - At startup the filesystem encoding is checked to verify it is U
TF-8. If not, the process exits with an error reporting the errant encoding.
- ansible-test - At startup the locale is configured as ``en_US.UTF-8``, with a
fallback to ``C.UTF-8``. If neither encoding is available the process exits with
an error. If the fallback is used, a warning is displayed. In previous versions
the ``en_US.UTF-8`` locale was always requested. However, no startup checking w
as performed to verify the locale was successfully configured.
amazon.aws amazon.aws
~~~~~~~~~~ ~~~~~~~~~~
- amazon.aws collection - The amazon.aws collection has dropped support for ``bo tocore<1.20.0`` and ``boto3<1.17.0``. Most modules will continue to work with ol der versions of the AWS SDK, however compatability with older versions of the SD K 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/am azon.aws/pull/574).
- autoscaling_group - The module has been migrated from the ``community.aws`` co llection. Playbooks using the Fully Qualified Collection Name for this module sh ould be updated to use ``amazon.aws.autoscaling_group``. - autoscaling_group - The module has been migrated from the ``community.aws`` co llection. Playbooks using the Fully Qualified Collection Name for this module sh ould be updated to use ``amazon.aws.autoscaling_group``.
- autoscaling_group_info - The module has been migrated from the ``community.aws `` collection. Playbooks using the Fully Qualified Collection Name for this modu le should be updated to use ``amazon.aws.autoscaling_group_info``. - autoscaling_group_info - The module has been migrated from the ``community.aws `` collection. Playbooks using the Fully Qualified Collection Name for this modu le should be updated to use ``amazon.aws.autoscaling_group_info``.
- cloudtrail - The module has been migrated from the ``community.aws`` collectio n. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.cloudtrail``. - cloudtrail - The module has been migrated from the ``community.aws`` collectio n. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.cloudtrail``.
- cloudwatch_metric_alarm - The module has been migrated from the ``community.aw s`` collection. Playbooks using the Fully Qualified Collection Name for this mod ule should be updated to use ``amazon.aws.cloudwatch_metric_alarm``. - cloudwatch_metric_alarm - The module has been migrated from the ``community.aw s`` collection. Playbooks using the Fully Qualified Collection Name for this mod ule should be updated to use ``amazon.aws.cloudwatch_metric_alarm``.
- cloudwatchevent_rule - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.cloudwatchevent_rule``. - cloudwatchevent_rule - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.cloudwatchevent_rule``.
- cloudwatchlogs_log_group - The module has been migrated from the ``community.a ws`` collection. Playbooks using the Fully Qualified Collection Name for this mo dule should be updated to use ``amazon.aws.cloudwatchlogs_log_group``. - cloudwatchlogs_log_group - The module has been migrated from the ``community.a ws`` collection. Playbooks using the Fully Qualified Collection Name for this mo dule should be updated to use ``amazon.aws.cloudwatchlogs_log_group``.
- cloudwatchlogs_log_group_info - The module has been migrated from the ``commun ity.aws`` collection. Playbooks using the Fully Qualified Collection Name for th is module should be updated to use ``amazon.aws.cloudwatchlogs_log_group_info``. - cloudwatchlogs_log_group_info - The module has been migrated from the ``commun ity.aws`` collection. Playbooks using the Fully Qualified Collection Name for th is module should be updated to use ``amazon.aws.cloudwatchlogs_log_group_info``.
- cloudwatchlogs_log_group_metric_filter - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Na me for this module should be updated to use ``amazon.aws.cloudwatchlogs_log_grou p_metric_filter``. - cloudwatchlogs_log_group_metric_filter - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Na me for this module should be updated to use ``amazon.aws.cloudwatchlogs_log_grou p_metric_filter``.
- ec2_eip - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be up dated to use ``amazon.aws.ec2_eip``. - ec2_eip - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be up dated to use ``amazon.aws.ec2_eip``.
- ec2_eip_info - The module has been migrated from the ``community.aws`` collect ion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.ec2_eip_info``. - ec2_eip_info - The module has been migrated from the ``community.aws`` collect ion. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.ec2_eip_info``.
skipping to change at line 267 skipping to change at line 356
- Remove following EOS dprecated modules - Remove following EOS dprecated modules
- Use of connection: local and the provider option are no longer valid on any mo dules in this collection. - Use of connection: local and the provider option are no longer valid on any mo dules in this collection.
- eos_interface - eos_interface
- eos_l2_interface - eos_l2_interface
- eos_l3_interface - eos_l3_interface
- eos_linkagg - eos_linkagg
- eos_static_route - eos_static_route
- eos_vlan - eos_vlan
check_point.mgmt
~~~~~~~~~~~~~~~~
- plugins/httpapi/checkpoint - Support for Smart-1 Cloud with new variable 'ansi
ble_cloud_mgmt_id'
chocolatey.chocolatey
~~~~~~~~~~~~~~~~~~~~~
- win_chocolatey - Added bootstrap_script option to allow users to target a scri
pt URL for installing Chocolatey on clients.
- win_chocolatey_facts - Added outdated packages list to data returned.
cisco.asa cisco.asa
~~~~~~~~~ ~~~~~~~~~
- Please use either of the following connection types - network_cli, httpapi or netconf. - Please use either of the following connection types - network_cli, httpapi or netconf.
- This includes the following modules: - This includes the following modules:
- This release drops support for `connection: local` and provider dictionary. - This release drops support for `connection: local` and provider dictionary.
- This release removes all deprecated plugins that have reached their end-of-lif e. - This release removes all deprecated plugins that have reached their end-of-lif e.
- Use of connection: local and the provider option are no longer valid on any mo dules in this collection. - Use of connection: local and the provider option are no longer valid on any mo dules in this collection.
- asa_acl - asa_acl
- asa_og - asa_og
skipping to change at line 296 skipping to change at line 396
- Only valid connection types for this collection are network_cli and netconf. - Only valid connection types for this collection are network_cli and netconf.
- This release drops support for `connection: local` and provider dictionary. - This release drops support for `connection: local` and provider dictionary.
cisco.nxos cisco.nxos
~~~~~~~~~~ ~~~~~~~~~~
- Please use either of the following connection types - network_cli, httpapi or netconf. - Please use either of the following connection types - network_cli, httpapi or netconf.
- This release drops support for `connection: local` and provider dictionary. - This release drops support for `connection: local` and provider dictionary.
community.general
~~~~~~~~~~~~~~~~~
- newrelic_deployment - removed New Relic v1 API, added support for v2 API (http
s://github.com/ansible-collections/community.general/pull/5341).
dellemc.openmanage
~~~~~~~~~~~~~~~~~~
- idrac_bios - The module is enhanced to support clear pending BIOS attributes,
reset BIOS to default settings, and configure BIOS attribute using Redfish.
infoblox.nios_modules
~~~~~~~~~~~~~~~~~~~~~
- Feature for extra layer security , with ``cert`` and ``key`` parameters in pla
ybooks for authenticating using certificate and key ``*.pem`` file absolute path
`#154 <https://github.com/infobloxopen/infoblox-ansible/pull/154>`_
- Fix to remove issue causing due to template attr in deleting network using Ans
ible module nios network `#147 <https://github.com/infobloxopen/infoblox-ansible
/pull/147>`_
junipernetworks.junos
~~~~~~~~~~~~~~~~~~~~~
- Use of connection: local and the provider option are no longer valid on any mo
dules in this collection.
vyos.vyos
~~~~~~~~~
- Use of connection: local and the provider option are no longer valid on any mo
dules in this collection.
Removed Features
ansible.netcommon
~~~~~~~~~~~~~~~~~
- napalm - Removed unused connection plugin.
- net_banner - Use <network_os>_banner instead.
- net_interface - Use <network_os>_interfaces instead.
- net_l2_interface - Use <network_os>_l2_interfaces instead.
- net_l3_interface - Use <network_os>_l3_interfaces instead.
- net_linkagg - Use <network_os>_lag_interfaces instead.
- net_lldp - Use <network_os>_lldp_global instead.
- net_lldp_interface - Use <network_os>_lldp_interfaces instead.
- net_logging - Use <network_os>_logging_global instead.
- net_static_route - Use <network_os>_static_routes instead.
- net_system - Use <network_os>_system instead.
- net_user - Use <network_os>_user instead.
- net_vlan - Use <network_os>_vlans instead.
- net_vrf - Use <network_os>_vrf instead.
cisco.ios
~~~~~~~~~
- ios_interface - use ios_interfaces instead.
- ios_l2_interface - use ios_l2_interfaces instead.
- ios_l3_interface - use ios_l3_interfaces instead.
- ios_static_route - use ios_static_routes instead.
- ios_vlan - use ios_vlans instead.
cisco.iosxr
~~~~~~~~~~~
- iosxr_interface - use iosxr_interfaces instead.
cisco.nxos
~~~~~~~~~~
- This release removes the following deprecated plugins that have reached their
end-of-life.
- nxos_acl
- nxos_acl_interface
- nxos_interface
- nxos_interface_ospf
- nxos_l2_interface
- nxos_l3_interface
- nxos_linkagg
- nxos_lldp
- nxos_ospf
- nxos_ospf_vrf
- nxos_smu
- nxos_static_route
- nxos_vlan
community.vmware
~~~~~~~~~~~~~~~~
- vca_fw - The deprecated module ``vca_fw`` has been removed.
- vca_nat - The deprecated module ``vca_nat`` has been removed.
- vca_vapp - The deprecated module ``vca_vapp`` has been removed.
- vmware_dns_config - The deprecated module ``vmware_dns_config`` has been remov
ed, you can use ``vmware_host_dns`` instead.
- vmware_guest_network - The deprecated parameter ``networks`` has been removed,
use loops to handle multiple interfaces (https://github.com/ansible-collections
/community.vmware/pull/1459).
- vmware_guest_vnc - The deprecated module ``vmware_guest_vnc`` has been removed
. The VNC support has been dropped with vSphere 7 and later (https://github.com/
ansible-collections/community.vmware/pull/1454).
- vmware_host_firewall_manager - The module doesn't accept a list for ``allowed_
hosts`` anymore, use a dict instead. Additionally, ``all_ip`` is now a required
sub-option of ``allowed_hosts`` (https://github.com/ansible-collections/communit
y.vmware/pull/1463).
- vsphere_copy - The deprecated parameters ``host`` and ``login`` have been remo
ved. Use ``hostname`` and ``username`` instead (https://github.com/ansible-colle
ctions/community.vmware/pull/1456).
junipernetworks.junos
~~~~~~~~~~~~~~~~~~~~~
- Remove following deprecated Junos Modules.
- junos_interface
- junos_l2_interface
- junos_l3_interface
- junos_linkagg
- junos_lldp
- junos_lldp_interface
- junos_static_route
- junos_vlan
vyos.vyos
~~~~~~~~~
- vyos_interface - use vyos_interfaces instead.
- vyos_l3_interface - use vyos_l3_interfaces instead.
- vyos_linkagg - use vyos_lag_interfaces instead.
- vyos_lldp - use vyos_lldp_global instead.
- vyos_lldp_interface - use vyos_lldp_interfaces instead.
- vyos_static_route - use vyos_static_routes instead.
Deprecated Features
- The dellemc.os10 collection is considered unmaintained and will be removed fro
m Ansible 8 if no one starts maintaining it again before Ansible 8. See `the rem
oval process for details on how this works <https://github.com/ansible-collectio
ns/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmainta
ined-collection>`__ (https://github.com/ansible-community/community-topics/issue
s/134).
- The dellemc.os6 collection is considered unmaintained and will be removed from
Ansible 8 if no one starts maintaining it again before Ansible 8. See `the remo
val process for details on how this works <https://github.com/ansible-collection
s/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmaintai
ned-collection>`__ (https://github.com/ansible-community/community-topics/issues
/132).
- The dellemc.os9 collection is considered unmaintained and will be removed from
Ansible 8 if no one starts maintaining it again before Ansible 8. See `the remo
val process for details on how this works <https://github.com/ansible-collection
s/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmaintai
ned-collection>`__ (https://github.com/ansible-community/community-topics/issues
/133).
- The mellanox.onyx collection is considered unmaintained and will be removed fr
om Ansible 8 if no one starts maintaining it again before Ansible 8. See `the re
moval process for details on how this works <https://github.com/ansible-collecti
ons/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmaint
ained-collection>`__ (https://github.com/ansible-community/community-topics/issu
es/136).
amazon.aws
~~~~~~~~~~
- 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-poli
cy-updates-for-aws-sdks-and-tools/) support for Python less than 3.7 by this col
lection has been deprecated and will be removed in a release after 2023-05-31 (h
ttps://github.com/ansible-collections/amazon.aws/pull/935).
- inventory/aws_ec2 - the ``include_extra_api_calls`` is now deprecated, its val
ue is silently ignored (https://github.com/ansible-collections/amazon.aws/pull/1
097).
cisco.mso
~~~~~~~~~
- The mso_schema_template_contract_filter contract_filter_type attribute is depr
ecated. The value is now deduced from filter_type.
community.aws
~~~~~~~~~~~~~
- community.aws collection - due to the AWS SDKs announcing the end of support f
or Python less than 3.7 (https://aws.amazon.com/blogs/developer/python-support-p
olicy-updates-for-aws-sdks-and-tools/) support for Python less than 3.7 by this
collection has been deprecated and will be removed in a release after 2023-05-31
(https://github.com/ansible-collections/community.aws/pull/1361).
community.general
~~~~~~~~~~~~~~~~~
- ArgFormat module utils - deprecated along ``CmdMixin``, in favor of the ``cmd_
runner_fmt`` module util (https://github.com/ansible-collections/community.gener
al/pull/5370).
- CmdMixin module utils - deprecated in favor of the ``CmdRunner`` module util (
https://github.com/ansible-collections/community.general/pull/5370).
- CmdModuleHelper module utils - deprecated in favor of the ``CmdRunner`` module
util (https://github.com/ansible-collections/community.general/pull/5370).
- CmdStateModuleHelper module utils - deprecated in favor of the ``CmdRunner`` m
odule util (https://github.com/ansible-collections/community.general/pull/5370).
- django_manage - support for Django releases older than 4.1 has been deprecated
and will be removed in community.general 9.0.0 (https://github.com/ansible-coll
ections/community.general/pull/5400).
- django_manage - support for the commands ``cleanup``, ``syncdb`` and ``validat
e`` that have been deprecated in Django long time ago will be removed in communi
ty.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/
5400).
- django_manage - the behavior of "creating the virtual environment when missing
" is being deprecated and will be removed in community.general version 9.0.0 (ht
tps://github.com/ansible-collections/community.general/pull/5405).
- lxc_container - the module will no longer make any effort to support Python 2
(https://github.com/ansible-collections/community.general/pull/5304).
- newrelic_deployment - ``appname`` and ``environment`` are no longer valid opti
ons in the v2 API. They will be removed in community.general 7.0.0 (https://gith
ub.com/ansible-collections/community.general/pull/5341).
Porting Guide for v7.0.0a1
==========================
Added Collections
- 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)
Known Issues
dellemc.openmanage
~~~~~~~~~~~~~~~~~~
- 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 ch
anges or a configuration job is in progress``. Wait for the job to complete and
run the task again.
- ome_application_alerts_smtp - Issue(212310) - The module does not provide a pr
oper error message if the destination_address is more than 255 characters.
- 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_local_access_configuration - Issue(215035) - The module reports ``S
uccessfully updated the local access setting`` if an unsupported value is provid
ed for the parameter timeout_limit. However, this value is not actually applied
on OpenManage Enterprise Modular.
- ome_device_local_access_configuration - Issue(217865) - The module does not di
splay a proper error message if an unsupported value is provided for the user_de
fined and lcd_language parameters.
- ome_device_network_services - Issue(212681) - The module does not provide a pr
oper error message if unsupported values are provided for the parameters- port_n
umber, 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_device_quick_deploy - Issue(216352) - The module does not display a proper
error message if an unsupported value is provided for the ipv6_prefix_length an
d vlan_id parameters.
- ome_smart_fabric_uplink - Issue(186024) - The module does not allow the creati
on of multiple uplinks of the same name even though it is supported by OpenManag
e Enterprise Modular. If an uplink is created using the same name as an existing
uplink, the existing uplink is modified.
netapp.ontap
~~~~~~~~~~~~
- na_ontap_snapshot - added documentation to use UTC format for ``expiry_time``.
Breaking Changes
- Ansible 7 requires Python 3.9 on the controller, same as ansible-core 2.14.
Ansible-core
~~~~~~~~~~~~
- Allow for lazy evaluation of Jinja2 expressions (https://github.com/ansible/an
sible/issues/56017)
- The default ansible-galaxy role skeletons no longer contain .travis.yml files.
You can configure ansible-galaxy to use a custom role skeleton that contains a
.travis.yml file to continue using Galaxy's integration with Travis CI.
- ansible - At startup the filesystem encoding and locale are checked to verify
they are UTF-8. If not, the process exits with an error reporting the errant enc
oding.
- ansible - Increase minimum Python requirement to Python 3.9 for CLI utilities
and controller code
- ansible-test - At startup the filesystem encoding is checked to verify it is U
TF-8. If not, the process exits with an error reporting the errant encoding.
- ansible-test - At startup the locale is configured as ``en_US.UTF-8``, with a
fallback to ``C.UTF-8``. If neither encoding is available the process exits with
an error. If the fallback is used, a warning is displayed. In previous versions
the ``en_US.UTF-8`` locale was always requested. However, no startup checking w
as performed to verify the locale was successfully configured.
- strategy plugins - Make ``ignore_unreachable`` to increase ``ignored`` and ``o
k`` and counter, not ``skipped`` and ``unreachable``. (https://github.com/ansib
le/ansible/issues/77690)
amazon.aws
~~~~~~~~~~
- Tags beginning with ``aws:`` will not be removed when purging tags, these tags
are reserved by Amazon and may not be updated or deleted (https://github.com/an
sible-collections/amazon.aws/issues/817).
- amazon.aws collection - the ``profile`` parameter is now mutually exclusive wi
th the ``aws_access_key``, ``aws_secret_key`` and ``security_token`` parameters
(https://github.com/ansible-collections/amazon.aws/pull/834).
- aws_az_info - the module alias ``aws_az_facts`` was deprecated in Ansible 2.9
and has now been removed (https://github.com/ansible-collections/amazon.aws/pull
/832).
- aws_s3 - the default value for ``ensure overwrite`` has been changed to ``diff
erent`` instead of ``always`` so that the module is idempotent by default (https
://github.com/ansible-collections/amazon.aws/issues/811).
- aws_ssm - on_denied and on_missing now both default to error, for consistency
with both aws_secret and the base Lookup class (https://github.com/ansible-colle
ctions/amazon.aws/issues/617).
- ec2 - The ``ec2`` module has been removed in release 4.0.0 and replaced by the
``ec2_instance`` module (https://github.com/ansible-collections/amazon.aws/pull
/630).
- ec2_vpc_igw_info - The default value for ``convert_tags`` has been changed to
``True`` (https://github.com/ansible-collections/amazon.aws/pull/835).
- elb_classic_lb - the ``ec2_elb`` fact has been removed (https://github.com/ans
ible-collections/amazon.aws/pull/827).
- module_utils - Support for the original AWS SDK aka ``boto`` has been removed,
including all relevant helper functions. All modules should now use the ``boto3
``/``botocore`` AWS SDK (https://github.com/ansible-collections/amazon.aws/pull/
630)
check_point.mgmt
~~~~~~~~~~~~~~~~
- cp_mgmt_access_role - the 'machines' parameter now accepts a single str and a
new parameter 'machines_list' of type dict has been added. the 'users' parameter
now accepts a single str and a new parameter 'users_list' of type dict has been
added.
- cp_mgmt_access_rule - the 'vpn' parameter now accepts a single str and a new p
arameter 'vpn_list' of type dict has been added. the 'position_by_rule' paramete
r has been changed to 'relative_position' with support of positioning above/belo
w a section (and not just a rule). the 'relative_position' parameter has also 't
op' and 'bottom' suboptions which allows positioning a rule at the top and botto
m of a section respectively. a new parameter 'search_entire_rulebase' has been a
dded to allow the relative positioning to be unlimited (was previously limited t
o 50 rules)
- cp_mgmt_administrator - the 'permissions_profile' parameter now accepts a sing
le str and a new parameter 'permissions_profile_list' of type dict has been adde
d.
- cp_mgmt_publish - the 'uid' parameter has been removed.
community.aws
~~~~~~~~~~~~~
- Tags beginning with ``aws:`` will not be removed when purging tags, these tags
are reserved by Amazon and may not be updated or deleted (https://github.com/an
sible-collections/amazon.aws/issues/817).
- aws_secret - tags are no longer removed when the ``tags`` parameter is not set
. To remove all tags set ``tags={}`` (https://github.com/ansible-collections/co
mmunity.aws/issues/1146).
- community.aws collection - The ``community.aws`` collection has now dropped su
pport for and any requirements upon the original ``boto`` AWS SDK, and now uses
the ``boto3``/``botocore`` AWS SDK (https://github.com/ansible-collections/commu
nity.aws/pull/898).
- community.aws collection - the ``profile`` parameter is now mutually exclusive
with the ``aws_access_key``, ``aws_secret_key`` and ``security_token`` paramete
rs (https://github.com/ansible-collections/amazon.aws/pull/834).
- ec2_vpc_route_table - The module has been migrated from the ``community.aws``
collection. Playbooks using the Fully Qualified Collection Name for this module
should be updated to use ``amazon.aws.ec2_vpc_route_table``.
- ec2_vpc_route_table_info - The module has been migrated from the ``community.a
ws`` collection. Playbooks using the Fully Qualified Collection Name for this mo
dule should be updated to use ``amazon.aws.ec2_vpc_route_table_info``.
- elb_instance - the ``ec2_elbs`` fact has been removed, ``updated_elbs`` has be
en added the return values and includes the same information (https://github.com
/ansible-collections/community.aws/pull/1173).
- elb_network_lb - the default value of ``state`` has changed from ``absent`` to
``present`` (https://github.com/ansible-collections/community.aws/pull/1167).
- script_inventory_ec2 - The ec2.py inventory script has been moved to a new rep
ository. The script can now be downloaded from https://github.com/ansible-commun
ity/contrib-scripts/blob/main/inventory/ec2.py and has been removed from this co
llection. We recommend migrating from the script to the amazon.aws.ec2 inventory
plugin. (https://github.com/ansible-collections/community.aws/pull/898)
community.docker
~~~~~~~~~~~~~~~~
- This collection does not work with ansible-core 2.11 on Python 3.12+. Please e
ither upgrade to ansible-core 2.12+, or use Python 3.11 or earlier (https://gith
ub.com/ansible-collections/community.docker/pull/271).
- docker_container - ``exposed_ports`` is no longer ignored in ``comparisons``.
Before, its value was assumed to be identical with the value of ``published_port
s`` (https://github.com/ansible-collections/community.docker/pull/422).
- docker_container - ``log_options`` can no longer be specified when ``log_drive
r`` is not specified (https://github.com/ansible-collections/community.docker/pu
ll/422).
- docker_container - ``publish_all_ports`` is no longer ignored in ``comparisons
`` (https://github.com/ansible-collections/community.docker/pull/422).
- docker_container - ``restart_retries`` can no longer be specified when ``resta
rt_policy`` is not specified (https://github.com/ansible-collections/community.d
ocker/pull/422).
- docker_container - ``stop_timeout`` is no longer ignored for idempotency if to
ld to be not ignored in ``comparisons``. So far it defaulted to ``ignore`` there
, and setting it to ``strict`` had no effect (https://github.com/ansible-collect
ions/community.docker/pull/422).
- modules and plugins communicating directly with the Docker daemon - when conne
cting by SSH and not using ``use_ssh_client=true``, reject unknown host keys ins
tead of accepting them. This is only a breaking change relative to older communi
ty.docker 3.0.0 pre-releases or with respect to Docker SDK for Python < 6.0.0. D
ocker SDK for Python 6.0.0 will also include this change (https://github.com/ans
ible-collections/community.docker/pull/434).
dellemc.enterprise_sonic
~~~~~~~~~~~~~~~~~~~~~~~~
- bgp_af - Add the route_advertise_list dictionary to the argspec to replace the
deleted, obsolete advertise_prefix attribute used for SONiC 3.x images on the 1
.x branch of this collection. This change corresponds to a SONiC 4.0 OC YANG RES
T compliance change for the BGP AF REST API. It enables specification of a route
map in conjunction with each route advertisement prefix (https://github.com/ans
ible-collections/dellemc.enterprise_sonic/pull/63).
- bgp_af - remove the obsolete 'advertise_prefix' attribute from argspec and con
fig code. This and subsequent co-req replacement with the new route advertise li
st argument structure require corresponding changes in playbooks previoulsly use
d for configuring route advertise prefixes for SONiC 3.x images. (https://github
.com/ansible-collections/dellemc.enterprise_sonic/pull/60)
- bgp_neighbors - Replace the previously defined standalone "bfd" attribute with
a bfd dictionary containing multiple attributes. This change corresponds to the
revised SONiC 4.x implementation of OC YANG compatible REST APIs. Playbooks pre
viously using the bfd attributes for SONiC 3.x images must be modified for useon
SONiC 4.0 images to use the new definition for the bfd attribute argspec struct
ure (https://github.com/ansible-collections/dellemc.enterprise_sonic/pull/72).
- bgp_neighbors - Replace, for BGP peer groups, the previously defined standalon
e "bfd" attribute with a bfd dictionary containing multiple attributes. This cha
nge corresponds to the revised SONiC 4.x implementation of OC YANG compatible RE
ST APIs. Playbooks previously using the bfd attributes for SONiC 3.x images must
be modified for useon SONiC 4.0 images to use the new definition for the bfd at
tribute argspec structure (https://github.com/ansible-collections/dellemc.enterp
rise_sonic/pull/81).
Major Changes
Ansible-core
~~~~~~~~~~~~
- Move handler processing into new ``PlayIterator`` phase to use the configured
strategy (https://github.com/ansible/ansible/issues/65067)
- ansible - At startup the filesystem encoding and locale are checked to verify
they are UTF-8. If not, the process exits with an error reporting the errant enc
oding.
- ansible - Increase minimum Python requirement to Python 3.9 for CLI utilities
and controller code
- ansible-test - At startup the filesystem encoding is checked to verify it is U
TF-8. If not, the process exits with an error reporting the errant encoding.
- ansible-test - At startup the locale is configured as ``en_US.UTF-8``, with a
fallback to ``C.UTF-8``. If neither encoding is available the process exits with
an error. If the fallback is used, a warning is displayed. In previous versions
the ``en_US.UTF-8`` locale was always requested. However, no startup checking w
as performed to verify the locale was successfully configured.
amazon.aws
~~~~~~~~~~
- amazon.aws collection - The amazon.aws collection has dropped support for ``bo
tocore<1.20.0`` and ``boto3<1.17.0``. Most modules will continue to work with ol
der versions of the AWS SDK, however compatability with older versions of the SD
K 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/am
azon.aws/pull/574).
check_point.mgmt
~~~~~~~~~~~~~~~~
- plugins/httpapi/checkpoint - Support for Smart-1 Cloud with new variable 'ansi
ble_cloud_mgmt_id'
chocolatey.chocolatey
~~~~~~~~~~~~~~~~~~~~~
- win_chocolatey - Added bootstrap_script option to allow users to target a scri
pt URL for installing Chocolatey on clients.
- win_chocolatey_facts - Added outdated packages list to data returned.
community.aws community.aws
~~~~~~~~~~~~~ ~~~~~~~~~~~~~
- community.aws collection - The amazon.aws collection has dropped support for ` `botocore<1.20.0`` and ``boto3<1.17.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/956). - community.aws collection - The amazon.aws collection has dropped support for ` `botocore<1.20.0`` and ``boto3<1.17.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/956).
community.docker community.docker
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
- The collection now contains vendored code from the Docker SDK for Python to ta lk to the Docker daemon. Modules and plugins using this code no longer need the Docker SDK for Python installed on the machine the module or plugin is running o n (https://github.com/ansible-collections/community.docker/pull/398). - The collection now contains vendored code from the Docker SDK for Python to ta lk to the Docker daemon. Modules and plugins using this code no longer need the Docker SDK for Python installed on the machine the module or plugin is running o n (https://github.com/ansible-collections/community.docker/pull/398).
- docker_api connection plugin - no longer uses the Docker SDK for Python. It re quires ``requests`` to be installed, and depending on the features used has some more requirements. If the Docker SDK for Python is installed, these requirement s are likely met (https://github.com/ansible-collections/community.docker/pull/4 14). - docker_api connection plugin - no longer uses the Docker SDK for Python. It re quires ``requests`` to be installed, and depending on the features used has some more requirements. If the Docker SDK for Python is installed, these requirement s are likely met (https://github.com/ansible-collections/community.docker/pull/4 14).
skipping to change at line 603 skipping to change at line 423
- docker_image_info - no longer uses the Docker SDK for Python. It requires ``re quests`` to be installed, and depending on the features used has some more requi rements. If the Docker SDK for Python is installed, these requirements are likel y met (https://github.com/ansible-collections/community.docker/pull/405). - docker_image_info - no longer uses the Docker SDK for Python. It requires ``re quests`` to be installed, and depending on the features used has some more requi rements. If the Docker SDK for Python is installed, these requirements are likel y met (https://github.com/ansible-collections/community.docker/pull/405).
- docker_image_load - no longer uses the Docker SDK for Python. It requires ``re quests`` to be installed, and depending on the features used has some more requi rements. If the Docker SDK for Python is installed, these requirements are likel y met (https://github.com/ansible-collections/community.docker/pull/406). - docker_image_load - no longer uses the Docker SDK for Python. It requires ``re quests`` to be installed, and depending on the features used has some more requi rements. If the Docker SDK for Python is installed, these requirements are likel y met (https://github.com/ansible-collections/community.docker/pull/406).
- docker_login - no longer uses the Docker SDK for Python. It requires ``request s`` to be installed, and depending on the features used has some more requiremen ts. If the Docker SDK for Python is installed, these requirements are likely met (https://github.com/ansible-collections/community.docker/pull/407). - docker_login - no longer uses the Docker SDK for Python. It requires ``request s`` to be installed, and depending on the features used has some more requiremen ts. If the Docker SDK for Python is installed, these requirements are likely met (https://github.com/ansible-collections/community.docker/pull/407).
- docker_network - no longer uses the Docker SDK for Python. It requires ``reque sts`` to be installed, and depending on the features used has some more requirem ents. If the Docker SDK for Python is installed, these requirements are likely m et (https://github.com/ansible-collections/community.docker/pull/408). - docker_network - no longer uses the Docker SDK for Python. It requires ``reque sts`` to be installed, and depending on the features used has some more requirem ents. If the Docker SDK for Python is installed, these requirements are likely m et (https://github.com/ansible-collections/community.docker/pull/408).
- docker_network_info - no longer uses the Docker SDK for Python. It requires `` requests`` to be installed, and depending on the features used has some more req uirements. If the Docker SDK for Python is installed, these requirements are lik ely met (https://github.com/ansible-collections/community.docker/pull/409). - docker_network_info - no longer uses the Docker SDK for Python. It requires `` requests`` to be installed, and depending on the features used has some more req uirements. If the Docker SDK for Python is installed, these requirements are lik ely met (https://github.com/ansible-collections/community.docker/pull/409).
- docker_plugin - no longer uses the Docker SDK for Python. It requires ``reques ts`` to be installed, and depending on the features used has some more requireme nts. If the Docker SDK for Python is installed, these requirements are likely me t (https://github.com/ansible-collections/community.docker/pull/429). - docker_plugin - no longer uses the Docker SDK for Python. It requires ``reques ts`` to be installed, and depending on the features used has some more requireme nts. If the Docker SDK for Python is installed, these requirements are likely me t (https://github.com/ansible-collections/community.docker/pull/429).
- docker_prune - no longer uses the Docker SDK for Python. It requires ``request s`` to be installed, and depending on the features used has some more requiremen ts. If the Docker SDK for Python is installed, these requirements are likely met (https://github.com/ansible-collections/community.docker/pull/410). - docker_prune - no longer uses the Docker SDK for Python. It requires ``request s`` to be installed, and depending on the features used has some more requiremen ts. If the Docker SDK for Python is installed, these requirements are likely met (https://github.com/ansible-collections/community.docker/pull/410).
- docker_volume - no longer uses the Docker SDK for Python. It requires ``reques ts`` to be installed, and depending on the features used has some more requireme nts. If the Docker SDK for Python is installed, these requirements are likely me t (https://github.com/ansible-collections/community.docker/pull/411). - docker_volume - no longer uses the Docker SDK for Python. It requires ``reques ts`` to be installed, and depending on the features used has some more requireme nts. If the Docker SDK for Python is installed, these requirements are likely me t (https://github.com/ansible-collections/community.docker/pull/411).
- docker_volume_info - no longer uses the Docker SDK for Python. It requires ``r equests`` to be installed, and depending on the features used has some more requ irements. If the Docker SDK for Python is installed, these requirements are like ly met (https://github.com/ansible-collections/community.docker/pull/412). - docker_volume_info - no longer uses the Docker SDK for Python. It requires ``r equests`` to be installed, and depending on the features used has some more requ irements. If the Docker SDK for Python is installed, these requirements are like ly met (https://github.com/ansible-collections/community.docker/pull/412).
community.general
~~~~~~~~~~~~~~~~~
- The internal structure of the collection was changed for modules and action pl
ugins. These no longer live in a directory hierarchy ordered by topic, but inste
ad are now all in a single (flat) directory. This has no impact on users *assumi
ng they did not use internal FQCNs*. These will still work, but result in deprec
ation warnings. They were never officially supported and thus the redirects are
kept as a courtsey, and this is not labelled as a breaking change. Note that for
example the Ansible VScode plugin started recommending these internal names. If
you followed its recommendation, you will now have to change back to the short
names to avoid deprecation warnings, and potential errors in the future as these
redirects will be removed in community.general 9.0.0 (https://github.com/ansibl
e-collections/community.general/pull/5461).
- newrelic_deployment - removed New Relic v1 API, added support for v2 API (http
s://github.com/ansible-collections/community.general/pull/5341).
community.mysql community.mysql
~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~
- mysql_db - the ``pipefail`` argument's default value will be changed to ``true `` in community.mysql 4.0.0. If your target machines do not use ``bash`` as a de fault interpreter, set ``pipefail`` to ``false`` explicitly. However, we strongl y recommend setting up ``bash`` as a default and ``pipefail=true`` as it will pr otect you from getting broken dumps you don't know about (https://github.com/ans ible-collections/community.mysql/issues/407). - mysql_db - the ``pipefail`` argument's default value will be changed to ``true `` in community.mysql 4.0.0. If your target machines do not use ``bash`` as a de fault interpreter, set ``pipefail`` to ``false`` explicitly. However, we strongl y recommend setting up ``bash`` as a default and ``pipefail=true`` as it will pr otect you from getting broken dumps you don't know about (https://github.com/ans ible-collections/community.mysql/issues/407).
community.network
~~~~~~~~~~~~~~~~~
- The community.network collection no longer supports Ansible 2.9 and ansible-ba
se 2.10. While we take no active measures to prevent usage, we will remove compa
tibility code and other compatility measures that will effectively prevent using
most content from this collection with Ansible 2.9, and some content of this co
llection with ansible-base 2.10. Both Ansible 2.9 and ansible-base 2.10 will ver
y soon be End of Life and if you are still using them, you should consider upgra
ding to ansible-core 2.11 or later as soon as possible (https://github.com/ansib
le-collections/community.network/pull/426).
- The internal structure of the collection was changed for modules and action pl
ugins. These no longer live in a directory hierarchy ordered by topic, but inste
ad are now all in a single (flat) directory. This has no impact on users *assumi
ng they did not use internal FQCNs*. These will still work, but result in deprec
ation warnings. They were never officially supported and thus the redirects are
kept as a courtsey, and this is not labelled as a breaking change. Note that for
example the Ansible VScode plugin started recommending these internal names. If
you followed its recommendation, you will now have to change back to the short
names to avoid deprecation warnings, and potential errors in the future as these
redirects will be removed in community.network 8.0.0 (https://github.com/ansibl
e-collections/community.network/pull/482).
community.postgresql community.postgresql
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
- postgresql_user - the ``groups`` argument has been deprecated and will be remo ved in ``community.postgresql 3.0.0``. Please use the ``postgresql_membership`` module to specify group/role memberships instead (https://github.com/ansible-col lections/community.postgresql/issues/277). - postgresql_user - the ``groups`` argument has been deprecated and will be remo ved in ``community.postgresql 3.0.0``. Please use the ``postgresql_membership`` module to specify group/role memberships instead (https://github.com/ansible-col lections/community.postgresql/issues/277).
dellemc.enterprise_sonic dellemc.enterprise_sonic
~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~
- Added 'static_routes' module to collection (https://github.com/ansible-collect ions/dellemc.enterprise_sonic/pull/82). - Added 'static_routes' module to collection (https://github.com/ansible-collect ions/dellemc.enterprise_sonic/pull/82).
- Added a resource module for NTP support (https://github.com/ansible-collection s/dellemc.enterprise_sonic/pull/99). - Added a resource module for NTP support (https://github.com/ansible-collection s/dellemc.enterprise_sonic/pull/99).
- Added a resource module for support of prefix lists (https://github.com/ansibl e-collections/dellemc.enterprise_sonic/pull/100). - Added a resource module for support of prefix lists (https://github.com/ansibl e-collections/dellemc.enterprise_sonic/pull/100).
- Updated backend REST API request formats in all applicable modules for compati bility with SONiC 4.x openconfig YANG compliant REST APIs. (https://github.com/a nsible-collections/dellemc.enterprise_sonic/pull/53) - Updated backend REST API request formats in all applicable modules for compati bility with SONiC 4.x openconfig YANG compliant REST APIs. (https://github.com/a nsible-collections/dellemc.enterprise_sonic/pull/53)
dellemc.openmanage dellemc.openmanage
~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~
- Added collection metadata for creating execution environments. - Added collection metadata for creating execution environments.
- Refactored the Markdown (MD) files and content for better readability. - Refactored the Markdown (MD) files and content for better readability.
- The share parameters are deprecated from the following modules - idrac_network , idrac_timezone_ntp, dellemc_configure_idrac_eventing, dellemc_configure_idrac_ services, dellemc_idrac_lc_attributes, dellemc_system_lockdown_mode. - The share parameters are deprecated from the following modules - idrac_network , idrac_timezone_ntp, dellemc_configure_idrac_eventing, dellemc_configure_idrac_ services, dellemc_idrac_lc_attributes, dellemc_system_lockdown_mode.
- idrac_bios - The module is enhanced to support clear pending BIOS attributes, reset BIOS to default settings, and configure BIOS attribute using Redfish.
- idrac_boot - Support for configuring the boot settings on iDRAC. - idrac_boot - Support for configuring the boot settings on iDRAC.
- idrac_redfish_storage_controller - This module is enhanced to support LockVirt
ualDisk operation.
- idrac_virtual_media - This module allows to configure Remote File Share settin
gs.
- ome_device_group - The module is enhanced to support the removal of devices fr om a static device group. - ome_device_group - The module is enhanced to support the removal of devices fr om a static device group.
- ome_devices - Support for performing device-specific operations on OpenManage Enterprise. - ome_devices - Support for performing device-specific operations on OpenManage Enterprise.
fortinet.fortimanager
~~~~~~~~~~~~~~~~~~~~~
- Fix compatibility issue for ansible 2.9.x and ansible-base 2.10.x.
- Many fixes for Ansible sanity test warnings & errors.
- Support FortiManager Schema 7.2.0 , 98 new modules
- support Ansible changelogs.
fortinet.fortios fortinet.fortios
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
- Support Diff feature in check_mode. - Support Diff feature in check_mode.
- Support Fortios 7.2.0. - Support Fortios 7.2.0.
infoblox.nios_modules infoblox.nios_modules
~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
- Feature for extra layer security , with `cert` and `key` parameters in playboo
ks for authenticating using certificate and key ``*.pem`` file absolute path `#1
54 <https://github.com/infobloxopen/infoblox-ansible/pull/154>`_
- Fix to remove issue causing due to template attr in deleting network using Ans
ible module nios network `#147 <https://github.com/infobloxopen/infoblox-ansible
/pull/147>`_
- Update `text` field of TXT Record `#128 <https://github.com/infobloxopen/infob lox-ansible/pull/128>`_ - Update `text` field of TXT Record `#128 <https://github.com/infobloxopen/infob lox-ansible/pull/128>`_
- Update operation using `old_name` and `new_name` for the object with dummy nam e in `old_name` (which does not exist in system) will not create a new object in the system. An error will be thrown stating the object does not exist in the sy stem `#129 <https://github.com/infobloxopen/infoblox-ansible/pull/129>`_ - Update operation using `old_name` and `new_name` for the object with dummy nam e in `old_name` (which does not exist in system) will not create a new object in the system. An error will be thrown stating the object does not exist in the sy stem `#129 <https://github.com/infobloxopen/infoblox-ansible/pull/129>`_
junipernetworks.junos
~~~~~~~~~~~~~~~~~~~~~
- Use of connection: local and the provider option are no longer valid on any mo
dules in this collection.
vyos.vyos
~~~~~~~~~
- Use of connection: local and the provider option are no longer valid on any mo
dules in this collection.
Removed Collections Removed Collections
------------------- -------------------
- servicenow.servicenow (previously included version: 1.0.6) - servicenow.servicenow (previously included version: 1.0.6)
Removed Features Removed Features
---------------- ----------------
Ansible-core Ansible-core
~~~~~~~~~~~~ ~~~~~~~~~~~~
skipping to change at line 680 skipping to change at line 535
amazon.aws amazon.aws
~~~~~~~~~~ ~~~~~~~~~~
- cloudformation - the ``template_format`` option has been removed. It has been ignored by the module since Ansible 2.3 (https://github.com/ansible-collections/ amazon.aws/pull/833). - cloudformation - the ``template_format`` option has been removed. It has been ignored by the module since Ansible 2.3 (https://github.com/ansible-collections/ amazon.aws/pull/833).
- ec2_key - the ``wait_timeout`` option had no effect, was deprecated in release 1.0.0, and has now been removed (https://github.com/ansible-collections/amazon. aws/pull/830). - ec2_key - the ``wait_timeout`` option had no effect, was deprecated in release 1.0.0, and has now been removed (https://github.com/ansible-collections/amazon. aws/pull/830).
- ec2_key - the ``wait`` option had no effect, was deprecated in release 1.0.0, and has now been removed (https://github.com/ansible-collections/amazon.aws/pull /830). - ec2_key - the ``wait`` option had no effect, was deprecated in release 1.0.0, and has now been removed (https://github.com/ansible-collections/amazon.aws/pull /830).
- ec2_tag - the previously deprecated state ``list`` has been removed. To list tags on an EC2 resource the ``ec2_tag_info`` module can be used (https://github. com/ansible-collections/amazon.aws/pull/829). - ec2_tag - the previously deprecated state ``list`` has been removed. To list tags on an EC2 resource the ``ec2_tag_info`` module can be used (https://github. com/ansible-collections/amazon.aws/pull/829).
- ec2_vol - the previously deprecated state ``list`` has been removed. To list volumes the ``ec2_vol_info`` module can be used (https://github.com/ansible-coll ections/amazon.aws/pull/828). - ec2_vol - the previously deprecated state ``list`` has been removed. To list volumes the ``ec2_vol_info`` module can be used (https://github.com/ansible-coll ections/amazon.aws/pull/828).
- module_utils.batch - the class ``ansible_collections.amazon.aws.plugins.module _utils.batch.AWSConnection`` has been removed. Please use ``AnsibleAWSModule.cl ient()`` instead (https://github.com/ansible-collections/amazon.aws/pull/831). - module_utils.batch - the class ``ansible_collections.amazon.aws.plugins.module _utils.batch.AWSConnection`` has been removed. Please use ``AnsibleAWSModule.cl ient()`` instead (https://github.com/ansible-collections/amazon.aws/pull/831).
ansible.netcommon
~~~~~~~~~~~~~~~~~
- napalm - Removed unused connection plugin.
- net_banner - Use <network_os>_banner instead.
- net_interface - Use <network_os>_interfaces instead.
- net_l2_interface - Use <network_os>_l2_interfaces instead.
- net_l3_interface - Use <network_os>_l3_interfaces instead.
- net_linkagg - Use <network_os>_lag_interfaces instead.
- net_lldp - Use <network_os>_lldp_global instead.
- net_lldp_interface - Use <network_os>_lldp_interfaces instead.
- net_logging - Use <network_os>_logging_global instead.
- net_static_route - Use <network_os>_static_routes instead.
- net_system - Use <network_os>_system instead.
- net_user - Use <network_os>_user instead.
- net_vlan - Use <network_os>_vlans instead.
- net_vrf - Use <network_os>_vrf instead.
cisco.ios
~~~~~~~~~
- ios_interface - use ios_interfaces instead.
- ios_l2_interface - use ios_l2_interfaces instead.
- ios_l3_interface - use ios_l3_interfaces instead.
- ios_static_route - use ios_static_routes instead.
- ios_vlan - use ios_vlans instead.
cisco.iosxr
~~~~~~~~~~~
- iosxr_interface - use iosxr_interfaces instead.
cisco.nxos
~~~~~~~~~~
- This release removes the following deprecated plugins that have reached their
end-of-life.
- nxos_acl
- nxos_acl_interface
- nxos_interface
- nxos_interface_ospf
- nxos_l2_interface
- nxos_l3_interface
- nxos_linkagg
- nxos_lldp
- nxos_ospf
- nxos_ospf_vrf
- nxos_smu
- nxos_static_route
- nxos_vlan
community.aws community.aws
~~~~~~~~~~~~~ ~~~~~~~~~~~~~
- aws_kms_info - the unused and deprecated ``keys_attr`` parameter has been remo ved (https://github.com/ansible-collections/amazon.aws/pull/1172). - aws_kms_info - the unused and deprecated ``keys_attr`` parameter has been remo ved (https://github.com/ansible-collections/amazon.aws/pull/1172).
- data_pipeline - the ``version`` option has always been ignored and has been re moved (https://github.com/ansible-collections/community.aws/pull/1160" - data_pipeline - the ``version`` option has always been ignored and has been re moved (https://github.com/ansible-collections/community.aws/pull/1160"
- ec2_eip - The ``wait_timeout`` option has been removed. It has always been ign ored by the module (https://github.com/ansible-collections/community.aws/pull/11 59). - ec2_eip - The ``wait_timeout`` option has been removed. It has always been ign ored by the module (https://github.com/ansible-collections/community.aws/pull/11 59).
- ec2_lc - the ``associate_public_ip_address`` option has been removed. It has a lways been ignored by the module (https://github.com/ansible-collections/communi ty.aws/pull/1158). - ec2_lc - the ``associate_public_ip_address`` option has been removed. It has a lways been ignored by the module (https://github.com/ansible-collections/communi ty.aws/pull/1158).
- ec2_metric_alarm - support for using the ``<=``, ``<``, ``>`` and ``>=`` opera tors for comparison has been dropped. Please use ``LessThanOrEqualToThreshold``, ``LessThanThreshold``, ``GreaterThanThreshold`` or ``GreaterThanOrEqualToThresh old`` instead (https://github.com/ansible-collections/amazon.aws/pull/1164). - ec2_metric_alarm - support for using the ``<=``, ``<``, ``>`` and ``>=`` opera tors for comparison has been dropped. Please use ``LessThanOrEqualToThreshold``, ``LessThanThreshold``, ``GreaterThanThreshold`` or ``GreaterThanOrEqualToThresh old`` instead (https://github.com/ansible-collections/amazon.aws/pull/1164).
- ecs_ecr - The deprecated alias ``delete_policy`` has been removed. Please use ``purge_policy`` instead (https://github.com/ansible-collections/community.aws/ pull/1161). - ecs_ecr - The deprecated alias ``delete_policy`` has been removed. Please use ``purge_policy`` instead (https://github.com/ansible-collections/community.aws/ pull/1161).
- iam_managed_policy - the unused ``fail_on_delete`` parameter has been removed (https://github.com/ansible-collections/community.aws/pull/1168) - iam_managed_policy - the unused ``fail_on_delete`` parameter has been removed (https://github.com/ansible-collections/community.aws/pull/1168)
skipping to change at line 782 skipping to change at line 687
- Execution Environments built with community.docker no longer include docker-co mpose < 2.0.0. If you need to use it with the ``docker_compose`` module, please install that requirement manually (https://github.com/ansible-collections/commun ity.docker/pull/400). - Execution Environments built with community.docker no longer include docker-co mpose < 2.0.0. If you need to use it with the ``docker_compose`` module, please install that requirement manually (https://github.com/ansible-collections/commun ity.docker/pull/400).
- Support for Ansible 2.9 and ansible-base 2.10 has been removed. If you need su pport for Ansible 2.9 or ansible-base 2.10, please use community.docker 2.x.y (h ttps://github.com/ansible-collections/community.docker/pull/400). - Support for Ansible 2.9 and ansible-base 2.10 has been removed. If you need su pport for Ansible 2.9 or ansible-base 2.10, please use community.docker 2.x.y (h ttps://github.com/ansible-collections/community.docker/pull/400).
- Support for Docker API versions 1.20 to 1.24 has been removed. If you need sup port for these API versions, please use community.docker 2.x.y (https://github.c om/ansible-collections/community.docker/pull/400). - Support for Docker API versions 1.20 to 1.24 has been removed. If you need sup port for these API versions, please use community.docker 2.x.y (https://github.c om/ansible-collections/community.docker/pull/400).
- Support for Python 2.6 has been removed. If you need support for Python 2.6, p lease use community.docker 2.x.y (https://github.com/ansible-collections/communi ty.docker/pull/400). - Support for Python 2.6 has been removed. If you need support for Python 2.6, p lease use community.docker 2.x.y (https://github.com/ansible-collections/communi ty.docker/pull/400).
- Various modules - the default of ``tls_hostname`` (``localhost``) has been rem oved. If you want to continue using ``localhost``, you need to specify it explic itly (https://github.com/ansible-collections/community.docker/pull/363). - Various modules - the default of ``tls_hostname`` (``localhost``) has been rem oved. If you want to continue using ``localhost``, you need to specify it explic itly (https://github.com/ansible-collections/community.docker/pull/363).
- docker_container - the ``all`` value is no longer allowed in ``published_ports ``. Use ``publish_all_ports=true`` instead (https://github.com/ansible-collectio ns/community.docker/pull/399). - docker_container - the ``all`` value is no longer allowed in ``published_ports ``. Use ``publish_all_ports=true`` instead (https://github.com/ansible-collectio ns/community.docker/pull/399).
- docker_container - the default of ``command_handling`` was changed from ``comp atibility`` to ``correct``. Older versions were warning for every invocation of the module when this would result in a change of behavior (https://github.com/an sible-collections/community.docker/pull/399). - docker_container - the default of ``command_handling`` was changed from ``comp atibility`` to ``correct``. Older versions were warning for every invocation of the module when this would result in a change of behavior (https://github.com/an sible-collections/community.docker/pull/399).
- docker_stack - the return values ``out`` and ``err`` have been removed. Use `` stdout`` and ``stderr`` instead (https://github.com/ansible-collections/communit y.docker/pull/363). - docker_stack - the return values ``out`` and ``err`` have been removed. Use `` stdout`` and ``stderr`` instead (https://github.com/ansible-collections/communit y.docker/pull/363).
community.general
~~~~~~~~~~~~~~~~~
- bitbucket* modules - ``username`` is no longer an alias of ``workspace``, but
of ``user`` (https://github.com/ansible-collections/community.general/pull/5326)
.
- gem - the default of the ``norc`` option changed from ``false`` to ``true`` (h
ttps://github.com/ansible-collections/community.general/pull/5326).
- gitlab_group_members - ``gitlab_group`` must now always contain the full path,
and no longer just the name or path (https://github.com/ansible-collections/com
munity.general/pull/5326).
- keycloak_authentication - the return value ``flow`` has been removed. Use ``en
d_state`` instead (https://github.com/ansible-collections/community.general/pull
/5326).
- keycloak_group - the return value ``group`` has been removed. Use ``end_state`
` instead (https://github.com/ansible-collections/community.general/pull/5326).
- lxd_container - the default of the ``ignore_volatile_options`` option changed
from ``true`` to ``false`` (https://github.com/ansible-collections/community.gen
eral/pull/5326).
- mail callback plugin - the ``sender`` option is now required (https://github.c
om/ansible-collections/community.general/pull/5326).
- module_helper module utils - remove the ``VarDict`` attribute from ``ModuleHel
per``. Import ``VarDict`` from ``ansible_collections.community.general.plugins.m
odule_utils.mh.mixins.vars`` instead (https://github.com/ansible-collections/com
munity.general/pull/5326).
- proxmox inventory plugin - the default of the ``want_proxmox_nodes_ansible_hos
t`` option changed from ``true`` to ``false`` (https://github.com/ansible-collec
tions/community.general/pull/5326).
- vmadm - the ``debug`` option has been removed. It was not used anyway (https:/
/github.com/ansible-collections/community.general/pull/5326).
community.network
~~~~~~~~~~~~~~~~~
- aireos modules - removed deprecated ``connection: local`` support. Use ``conne
ction: network_cli`` instead (https://github.com/ansible-collections/community.n
etwork/pull/440).
- aireos modules - removed deprecated ``provider`` option. Use ``connection: net
work_cli`` instead (https://github.com/ansible-collections/community.network/pul
l/440).
- aruba modules - removed deprecated ``connection: local`` support. Use ``connec
tion: network_cli`` instead (https://github.com/ansible-collections/community.ne
twork/pull/440).
- aruba modules - removed deprecated ``provider`` option. Use ``connection: netw
ork_cli`` instead (https://github.com/ansible-collections/community.network/pull
/440).
- ce modules - removed deprecated ``connection: local`` support. Use ``connectio
n: network_cli`` instead (https://github.com/ansible-collections/community.netwo
rk/pull/440).
- ce modules - removed deprecated ``provider`` option. Use ``connection: network
_cli`` instead (https://github.com/ansible-collections/community.network/pull/44
0).
- enos modules - removed deprecated ``connection: local`` support. Use ``connect
ion: network_cli`` instead (https://github.com/ansible-collections/community.net
work/pull/440).
- enos modules - removed deprecated ``provider`` option. Use ``connection: netwo
rk_cli`` instead (https://github.com/ansible-collections/community.network/pull/
440).
- ironware modules - removed deprecated ``connection: local`` support. Use ``con
nection: network_cli`` instead (https://github.com/ansible-collections/community
.network/pull/440).
- ironware modules - removed deprecated ``provider`` option. Use ``connection: n
etwork_cli`` instead (https://github.com/ansible-collections/community.network/p
ull/440).
- sros modules - removed deprecated ``connection: local`` support. Use ``connect
ion: network_cli`` instead (https://github.com/ansible-collections/community.net
work/pull/440).
- sros modules - removed deprecated ``provider`` option. Use ``connection: netwo
rk_cli`` instead (https://github.com/ansible-collections/community.network/pull/
440).
community.vmware
~~~~~~~~~~~~~~~~
- vca_fw - The deprecated module ``vca_fw`` has been removed.
- vca_nat - The deprecated module ``vca_nat`` has been removed.
- vca_vapp - The deprecated module ``vca_vapp`` has been removed.
- vmware_dns_config - The deprecated module ``vmware_dns_config`` has been remov
ed, you can use ``vmware_host_dns`` instead.
- vmware_guest_network - The deprecated parameter ``networks`` has been removed,
use loops to handle multiple interfaces (https://github.com/ansible-collections
/community.vmware/pull/1459).
- vmware_guest_vnc - The deprecated module ``vmware_guest_vnc`` has been removed
. The VNC support has been dropped with vSphere 7 and later (https://github.com/
ansible-collections/community.vmware/pull/1454).
- vmware_host_firewall_manager - The module doesn't accept a list for ``allowed_
hosts`` anymore, use a dict instead. Additionally, ``all_ip`` is now a required
sub-option of ``allowed_hosts`` (https://github.com/ansible-collections/communit
y.vmware/pull/1463).
- vsphere_copy - The deprecated parameters ``host`` and ``login`` have been remo
ved. Use ``hostname`` and ``username`` instead (https://github.com/ansible-colle
ctions/community.vmware/pull/1456).
junipernetworks.junos
~~~~~~~~~~~~~~~~~~~~~
- Remove following deprecated Junos Modules.
- junos_interface
- junos_l2_interface
- junos_l3_interface
- junos_linkagg
- junos_lldp
- junos_lldp_interface
- junos_static_route
- junos_vlan
vyos.vyos
~~~~~~~~~
- vyos_interface - use vyos_interfaces instead.
- vyos_l3_interface - use vyos_l3_interfaces instead.
- vyos_linkagg - use vyos_lag_interfaces instead.
- vyos_lldp - use vyos_lldp_global instead.
- vyos_lldp_interface - use vyos_lldp_interfaces instead.
- vyos_static_route - use vyos_static_routes instead.
Deprecated Features Deprecated Features
------------------- -------------------
- The dellemc.os10 collection is considered unmaintained and will be removed fro
m Ansible 8 if no one starts maintaining it again before Ansible 8. See `the rem
oval process for details on how this works <https://github.com/ansible-collectio
ns/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmainta
ined-collection>`__ (https://github.com/ansible-community/community-topics/issue
s/134).
- The dellemc.os6 collection is considered unmaintained and will be removed from
Ansible 8 if no one starts maintaining it again before Ansible 8. See `the remo
val process for details on how this works <https://github.com/ansible-collection
s/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmaintai
ned-collection>`__ (https://github.com/ansible-community/community-topics/issues
/132).
- The dellemc.os9 collection is considered unmaintained and will be removed from
Ansible 8 if no one starts maintaining it again before Ansible 8. See `the remo
val process for details on how this works <https://github.com/ansible-collection
s/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmaintai
ned-collection>`__ (https://github.com/ansible-community/community-topics/issues
/133).
- The google.cloud collection is considered unmaintained and will be removed fro m Ansible 8 if no one starts maintaining it again before Ansible 8. See `the rem oval process for details on how this works <https://github.com/ansible-collectio ns/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmainta ined-collection>`__ (https://github.com/ansible-community/community-topics/issue s/105). - The google.cloud collection is considered unmaintained and will be removed fro m Ansible 8 if no one starts maintaining it again before Ansible 8. See `the rem oval process for details on how this works <https://github.com/ansible-collectio ns/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmainta ined-collection>`__ (https://github.com/ansible-community/community-topics/issue s/105).
- The mellanox.onyx collection is considered unmaintained and will be removed fr om Ansible 8 if no one starts maintaining it again before Ansible 8. See `the re moval process for details on how this works <https://github.com/ansible-collecti ons/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmaint ained-collection>`__ (https://github.com/ansible-community/community-topics/issu es/136).
Ansible-core Ansible-core
~~~~~~~~~~~~ ~~~~~~~~~~~~
- Deprecate ability of lookup plugins to return arbitrary data. Lookup plugins m ust return lists, failing to do so will be an error in 2.18. (https://github.com /ansible/ansible/issues/77788) - Deprecate ability of lookup plugins to return arbitrary data. Lookup plugins m ust return lists, failing to do so will be an error in 2.18. (https://github.com /ansible/ansible/issues/77788)
- Encryption - Deprecate use of the Python crypt module due to it's impending re moval from Python 3.13 - Encryption - Deprecate use of the Python crypt module due to it's impending re moval from Python 3.13
- PlayContext.verbosity is deprecated and will be removed in 2.18. Use ansible.u tils.display.Display().verbosity as the single source of truth. - PlayContext.verbosity is deprecated and will be removed in 2.18. Use ansible.u tils.display.Display().verbosity as the single source of truth.
- ``DEFAULT_FACT_PATH``, ``DEFAULT_GATHER_SUBSET`` and ``DEFAULT_GATHER_TIMEOUT` ` are deprecated and will be removed in 2.18. Use ``module_defaults`` keyword in stead. - ``DEFAULT_FACT_PATH``, ``DEFAULT_GATHER_SUBSET`` and ``DEFAULT_GATHER_TIMEOUT` ` are deprecated and will be removed in 2.18. Use ``module_defaults`` keyword in stead.
- ``PlayIterator`` - deprecate ``cache_block_tasks`` and ``get_original_task`` w hich are noop and unused. - ``PlayIterator`` - deprecate ``cache_block_tasks`` and ``get_original_task`` w hich are noop and unused.
- ``Templar`` - deprecate ``shared_loader_obj`` option which is unused. ``ansibl e.plugins.loader`` is used directly instead. - ``Templar`` - deprecate ``shared_loader_obj`` option which is unused. ``ansibl e.plugins.loader`` is used directly instead.
- listify_lookup_plugin_terms, deprecate 'loader/dataloader' parameter as it not used. - listify_lookup_plugin_terms, deprecate 'loader/dataloader' parameter as it not used.
- vars plugins - determining whether or not to run ansible.legacy vars plugins w ith the class attribute REQUIRES_WHITELIST is deprecated, set REQUIRES_ENABLED i nstead. - vars plugins - determining whether or not to run ansible.legacy vars plugins w ith the class attribute REQUIRES_WHITELIST is deprecated, set REQUIRES_ENABLED i nstead.
amazon.aws amazon.aws
~~~~~~~~~~ ~~~~~~~~~~
- amazon.aws collection - Support for the ``EC2_ACCESS_KEY`` environment variabl
e has been deprecated and will be removed in a release after 2024-12-01. Please
use the ``access_key`` parameter or ``AWS_ACCESS_KEY_ID`` environment variable
instead (https://github.com/ansible-collections/amazon.aws/pull/1172).
- amazon.aws collection - Support for the ``EC2_REGION`` environment variable ha
s been deprecated and will be removed in a release after 2024-12-01. Please use
the ``region`` parameter or ``AWS_REGION`` environment variable instead (https:
//github.com/ansible-collections/amazon.aws/pull/1172).
- amazon.aws collection - Support for the ``EC2_SECRET_KEY`` environment variabl
e has been deprecated and will be removed in a release after 2024-12-01. Please
use the ``secret_key`` parameter or ``AWS_SECRET_ACCESS_KEY`` environment varia
ble instead (https://github.com/ansible-collections/amazon.aws/pull/1172).
- amazon.aws collection - Support for the ``EC2_SECURITY_TOKEN`` environment var
iable has been deprecated and will be removed in a release after 2024-12-01. Pl
ease use the ``session_token`` parameter or ``AWS_SESSION_TOKEN`` environment va
riable instead (https://github.com/ansible-collections/amazon.aws/pull/1172).
- amazon.aws collection - Support for the ``EC2_URL`` and ``S3_URL`` environment
variables has been deprecated and will be removed in a release after 2024-12-01
. Please use the ``endpoint_url`` parameter or ``AWS_ENDPOINT_URL`` environment
variable instead (https://github.com/ansible-collections/amazon.aws/pull/1172).
- amazon.aws collection - The ``access_token`` alias for the ``session_token`` p
arameter has been deprecated and will be removed in a release after 2024-12-01.
Please use the ``session_token`` name instead (https://github.com/ansible-colle
ctions/amazon.aws/pull/1172).
- amazon.aws collection - The ``aws_security_token`` alias for the ``session_tok
en`` parameter has been deprecated and will be removed in a release after 2024-1
2-01. Please use the ``session_token`` name instead (https://github.com/ansible
-collections/amazon.aws/pull/1172).
- amazon.aws collection - The ``ec2_access_key`` alias for the ``access_key`` pa
rameter has been deprecated and will be removed in a release after 2024-12-01.
Please use the ``access_key`` name instead (https://github.com/ansible-collectio
ns/amazon.aws/pull/1172).
- amazon.aws collection - The ``ec2_region`` alias for the ``region`` parameter
has been deprecated and will be removed in a release after 2024-12-01. Please u
se the ``region`` name instead (https://github.com/ansible-collections/amazon.aw
s/pull/1172).
- amazon.aws collection - The ``ec2_secret_key`` alias for the ``secret_key`` pa
rameter has been deprecated and will be removed in a release after 2024-12-01.
Please use the ``secret_key`` name instead (https://github.com/ansible-collectio
ns/amazon.aws/pull/1172).
- amazon.aws collection - The ``security_token`` alias for the ``session_token``
parameter has been deprecated and will be removed in a release after 2024-12-01
. Please use the ``session_token`` name instead (https://github.com/ansible-col
lections/amazon.aws/pull/1172).
- 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-poli cy-updates-for-aws-sdks-and-tools/) support for Python less than 3.7 by this col lection has been deprecated and will be removed in a release after 2023-05-31 (h ttps://github.com/ansible-collections/amazon.aws/pull/935). - 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-poli cy-updates-for-aws-sdks-and-tools/) support for Python less than 3.7 by this col lection has been deprecated and will be removed in a release after 2023-05-31 (h ttps://github.com/ansible-collections/amazon.aws/pull/935).
- aws_s3 - The ``S3_URL`` alias for the s3_url option has been deprecated and wi ll be removed in release 5.0.0 (https://github.com/ansible-collections/community .aws/pull/795). - aws_s3 - The ``S3_URL`` alias for the s3_url option has been deprecated and wi ll be removed in release 5.0.0 (https://github.com/ansible-collections/community .aws/pull/795).
- ec2_ami - The ``DeviceName`` alias for the device_name option has been depreca ted and will be removed in release 5.0.0 (https://github.com/ansible-collections /community.aws/pull/795). - ec2_ami - The ``DeviceName`` alias for the device_name option has been depreca ted and will be removed in release 5.0.0 (https://github.com/ansible-collections /community.aws/pull/795).
- ec2_ami - The ``NoDevice`` alias for the no_device option has been deprecated and will be removed in release 5.0.0 (https://github.com/ansible-collections/com munity.aws/pull/795). - ec2_ami - The ``NoDevice`` alias for the no_device option has been deprecated and will be removed in release 5.0.0 (https://github.com/ansible-collections/com munity.aws/pull/795).
- ec2_ami - The ``VirtualName`` alias for the virtual_name option has been depre cated and will be removed in release 5.0.0 (https://github.com/ansible-collectio ns/community.aws/pull/795). - ec2_ami - The ``VirtualName`` alias for the virtual_name option has been depre cated and will be removed in release 5.0.0 (https://github.com/ansible-collectio ns/community.aws/pull/795).
- ec2_ami - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True`` (https://github.com/a nsible-collections/amazon.aws/pull/846). - ec2_ami - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True`` (https://github.com/a nsible-collections/amazon.aws/pull/846).
- ec2_instance - The default value for ```instance_type``` has been deprecated, in the future release you must set an instance_type or a launch_template (https: //github.com/ansible-collections/amazon.aws/pull/587). - ec2_instance - The default value for ```instance_type``` has been deprecated, in the future release you must set an instance_type or a launch_template (https: //github.com/ansible-collections/amazon.aws/pull/587).
- ec2_instance - the current default value of ``False`` for ``purge_tags`` has b een deprecated and will be updated in release 5.0.0 to ``True`` (https://github. com/ansible-collections/amazon.aws/pull/849). - ec2_instance - the current default value of ``False`` for ``purge_tags`` has b een deprecated and will be updated in release 5.0.0 to ``True`` (https://github. com/ansible-collections/amazon.aws/pull/849).
- ec2_key - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True`` (https://github.com/a nsible-collections/amazon.aws/pull/846). - ec2_key - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True`` (https://github.com/a nsible-collections/amazon.aws/pull/846).
- ec2_security_group - support for passing nested lists to ``cidr_ip`` and ``cid r_ipv6`` has been deprecated. Nested lists can be passed through the ``flatten`` filter instead ``cidr_ip: '{{ my_cidrs | flatten }}'`` (https://github.com/ansi ble-collections/amazon.aws/pull/1213).
- ec2_vol - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True`` (https://github.com/a nsible-collections/amazon.aws/pull/846). - ec2_vol - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True`` (https://github.com/a nsible-collections/amazon.aws/pull/846).
- ec2_vpc_dhcp_option_info - The ``DhcpOptionIds`` alias for the dhcp_option_ids option has been deprecated and will be removed in release 5.0.0 (https://github .com/ansible-collections/community.aws/pull/795). - ec2_vpc_dhcp_option_info - The ``DhcpOptionIds`` alias for the dhcp_option_ids option has been deprecated and will be removed in release 5.0.0 (https://github .com/ansible-collections/community.aws/pull/795).
- ec2_vpc_dhcp_option_info - The ``DryRun`` alias for the dry_run option has bee n deprecated and will be removed in release 5.0.0 (https://github.com/ansible-co llections/community.aws/pull/795). - ec2_vpc_dhcp_option_info - The ``DryRun`` alias for the dry_run option has bee n deprecated and will be removed in release 5.0.0 (https://github.com/ansible-co llections/community.aws/pull/795).
- ec2_vpc_endpoint - the current default value of ``False`` for ``purge_tags`` h as been deprecated and will be updated in release 5.0.0 to ``True`` (https://git hub.com/ansible-collections/amazon.aws/pull/846). - ec2_vpc_endpoint - the current default value of ``False`` for ``purge_tags`` h as been deprecated and will be updated in release 5.0.0 to ``True`` (https://git hub.com/ansible-collections/amazon.aws/pull/846).
- ec2_vpc_net - the current default value of ``False`` for ``purge_tags`` has be en deprecated and will be updated in release 5.0.0 to ``True`` (https://github.c om/ansible-collections/amazon.aws/pull/848). - ec2_vpc_net - the current default value of ``False`` for ``purge_tags`` has be en deprecated and will be updated in release 5.0.0 to ``True`` (https://github.c om/ansible-collections/amazon.aws/pull/848).
- ec2_vpc_route_table - the current default value of ``False`` for ``purge_tags` ` has been deprecated and will be updated in release 5.0.0 to ``True`` (https:// github.com/ansible-collections/amazon.aws/pull/846). - ec2_vpc_route_table - the current default value of ``False`` for ``purge_tags` ` has been deprecated and will be updated in release 5.0.0 to ``True`` (https:// github.com/ansible-collections/amazon.aws/pull/846).
- inventory/aws_ec2 - the ``include_extra_api_calls`` is now deprecated, its val ue is silently ignored (https://github.com/ansible-collections/amazon.aws/pull/1 097).
- module_utils.cloud - removal of the ``CloudRetry.backoff`` has been delayed un til release 6.0.0. It is recommended to update custom modules to use ``jittered _backoff`` or ``exponential_backoff`` instead (https://github.com/ansible-collec tions/amazon.aws/pull/951). - module_utils.cloud - removal of the ``CloudRetry.backoff`` has been delayed un til release 6.0.0. It is recommended to update custom modules to use ``jittered _backoff`` or ``exponential_backoff`` instead (https://github.com/ansible-collec tions/amazon.aws/pull/951).
- module_utils.url - ``ansible_collections.amazon.aws.module_utils.urls`` is bel ieved to be unused and has been deprecated and will be removed in release 7.0.0.
- s3_bucket - The ``S3_URL`` alias for the s3_url option has been deprecated and will be removed in release 5.0.0 (https://github.com/ansible-collections/commun ity.aws/pull/795). - s3_bucket - The ``S3_URL`` alias for the s3_url option has been deprecated and will be removed in release 5.0.0 (https://github.com/ansible-collections/commun ity.aws/pull/795).
- s3_object - Support for creation and deletion of S3 buckets has been deprecate d. Please use the ``amazon.aws.s3_bucket`` module to create and delete buckets (https://github.com/ansible-collections/amazon.aws/pull/869). - s3_object - Support for creation and deletion of S3 buckets has been deprecate d. Please use the ``amazon.aws.s3_bucket`` module to create and delete buckets (https://github.com/ansible-collections/amazon.aws/pull/869).
cisco.ios cisco.ios
~~~~~~~~~ ~~~~~~~~~
- Deprecated ios_linkagg_module in favor of ios_lag_interfaces. - Deprecated ios_linkagg_module in favor of ios_lag_interfaces.
cisco.mso
~~~~~~~~~
- The mso_schema_template_contract_filter contract_filter_type attribute is depr
ecated. The value is now deduced from filter_type.
community.aws community.aws
~~~~~~~~~~~~~ ~~~~~~~~~~~~~
- aws_acm - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True``. - aws_acm - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True``.
- aws_codebuild - The ``tags`` parameter currently uses a non-standard format an d has been deprecated. In release 6.0.0 this parameter will accept a simple key /value pair dictionary instead of the current list of dictionaries. It is recom mended to migrate to using the resource_tags parameter which already accepts the simple dictionary format (https://github.com/ansible-collections/community.aws/ pull/1221). - aws_codebuild - The ``tags`` parameter currently uses a non-standard format an d has been deprecated. In release 6.0.0 this parameter will accept a simple key /value pair dictionary instead of the current list of dictionaries. It is recom mended to migrate to using the resource_tags parameter which already accepts the simple dictionary format (https://github.com/ansible-collections/community.aws/ pull/1221).
- aws_glue_connection - the ``connection_parameters`` return key has been deprec ated and will be removed in a release after 2024-06-01, it is being replaced by the ``raw_connection_parameters`` key (https://github.com/ansible-collections/co mmunity.aws/pull/518). - aws_glue_connection - the ``connection_parameters`` return key has been deprec ated and will be removed in a release after 2024-06-01, it is being replaced by the ``raw_connection_parameters`` key (https://github.com/ansible-collections/co mmunity.aws/pull/518).
- aws_kms - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True``. - aws_kms - the current default value of ``False`` for ``purge_tags`` has been d eprecated and will be updated in release 5.0.0 to ``True``.
- cloudfront_distribution - the current default value of ``False`` for ``purge_t ags`` has been deprecated and will be updated in release 5.0.0 to ``True``. - cloudfront_distribution - the current default value of ``False`` for ``purge_t ags`` has been deprecated and will be updated in release 5.0.0 to ``True``.
- community.aws collection - due to the AWS SDKs announcing the end of support f or Python less than 3.7 (https://aws.amazon.com/blogs/developer/python-support-p olicy-updates-for-aws-sdks-and-tools/) support for Python less than 3.7 by this collection has been deprecated and will be removed in a release after 2023-05-31 (https://github.com/ansible-collections/community.aws/pull/1361). - community.aws collection - due to the AWS SDKs announcing the end of support f or Python less than 3.7 (https://aws.amazon.com/blogs/developer/python-support-p olicy-updates-for-aws-sdks-and-tools/) support for Python less than 3.7 by this collection has been deprecated and will be removed in a release after 2023-05-31 (https://github.com/ansible-collections/community.aws/pull/1361).
- ec2_vpc_vpn - the current default value of ``False`` for ``purge_tags`` has be en deprecated and will be updated in release 5.0.0 to ``True``. - ec2_vpc_vpn - the current default value of ``False`` for ``purge_tags`` has be en deprecated and will be updated in release 5.0.0 to ``True``.
skipping to change at line 855 skipping to change at line 848
community.crypto community.crypto
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
- Support for Ansible 2.9 and ansible-base 2.10 is deprecated, and will be remov ed in the next major release (community.crypto 3.0.0). Some modules might still work with these versions afterwards, but we will no longer keep compatibility co de that was needed to support them (https://github.com/ansible-collections/commu nity.crypto/pull/460). - Support for Ansible 2.9 and ansible-base 2.10 is deprecated, and will be remov ed in the next major release (community.crypto 3.0.0). Some modules might still work with these versions afterwards, but we will no longer keep compatibility co de that was needed to support them (https://github.com/ansible-collections/commu nity.crypto/pull/460).
community.docker community.docker
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
- Support for Docker API version 1.20 to 1.24 has been deprecated and will be re moved in community.docker 3.0.0. The first Docker version supporting API version 1.25 was Docker 1.13, released in January 2017. This affects the modules ``dock er_container``, ``docker_container_exec``, ``docker_container_info``, ``docker_c ompose``, ``docker_login``, ``docker_image``, ``docker_image_info``, ``docker_im age_load``, ``docker_host_info``, ``docker_network``, ``docker_network_info``, ` `docker_node_info``, ``docker_swarm_info``, ``docker_swarm_service``, ``docker_s warm_service_info``, ``docker_volume_info``, and ``docker_volume``, whose minima lly supported API version is between 1.20 and 1.24 (https://github.com/ansible-c ollections/community.docker/pull/396). - Support for Docker API version 1.20 to 1.24 has been deprecated and will be re moved in community.docker 3.0.0. The first Docker version supporting API version 1.25 was Docker 1.13, released in January 2017. This affects the modules ``dock er_container``, ``docker_container_exec``, ``docker_container_info``, ``docker_c ompose``, ``docker_login``, ``docker_image``, ``docker_image_info``, ``docker_im age_load``, ``docker_host_info``, ``docker_network``, ``docker_network_info``, ` `docker_node_info``, ``docker_swarm_info``, ``docker_swarm_service``, ``docker_s warm_service_info``, ``docker_volume_info``, and ``docker_volume``, whose minima lly supported API version is between 1.20 and 1.24 (https://github.com/ansible-c ollections/community.docker/pull/396).
- Support for Python 2.6 is deprecated and will be removed in the next major rel ease (community.docker 3.0.0). Some modules might still work with Python 2.6, bu t we will no longer try to ensure compatibility (https://github.com/ansible-coll ections/community.docker/pull/388). - Support for Python 2.6 is deprecated and will be removed in the next major rel ease (community.docker 3.0.0). Some modules might still work with Python 2.6, bu t we will no longer try to ensure compatibility (https://github.com/ansible-coll ections/community.docker/pull/388).
- docker_container - the ``ignore_image`` option is deprecated and will be remov
ed in community.docker 4.0.0. Use ``image: ignore`` in ``comparisons`` instead (
https://github.com/ansible-collections/community.docker/pull/487).
- docker_container - the ``purge_networks`` option is deprecated and will be rem
oved in community.docker 4.0.0. Use ``networks: strict`` in ``comparisons`` inst
ead, and make sure to provide ``networks``, with value ``[]`` if all networks sh
ould be removed (https://github.com/ansible-collections/community.docker/pull/48
7).
community.general community.general
~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~
- ArgFormat module utils - deprecated along ``CmdMixin``, in favor of the ``cmd_
runner_fmt`` module util (https://github.com/ansible-collections/community.gener
al/pull/5370).
- CmdMixin module utils - deprecated in favor of the ``CmdRunner`` module util (
https://github.com/ansible-collections/community.general/pull/5370).
- CmdModuleHelper module utils - deprecated in favor of the ``CmdRunner`` module
util (https://github.com/ansible-collections/community.general/pull/5370).
- CmdStateModuleHelper module utils - deprecated in favor of the ``CmdRunner`` m
odule util (https://github.com/ansible-collections/community.general/pull/5370).
- cmd_runner module utils - deprecated ``fmt`` in favour of ``cmd_runner_fmt`` a s the parameter format object (https://github.com/ansible-collections/community. general/pull/4777). - cmd_runner module utils - deprecated ``fmt`` in favour of ``cmd_runner_fmt`` a s the parameter format object (https://github.com/ansible-collections/community. general/pull/4777).
- django_manage - support for Django releases older than 4.1 has been deprecated
and will be removed in community.general 9.0.0 (https://github.com/ansible-coll
ections/community.general/pull/5400).
- django_manage - support for the commands ``cleanup``, ``syncdb`` and ``validat
e`` that have been deprecated in Django long time ago will be removed in communi
ty.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/
5400).
- django_manage - the behavior of "creating the virtual environment when missing
" is being deprecated and will be removed in community.general version 9.0.0 (ht
tps://github.com/ansible-collections/community.general/pull/5405).
- gconftool2 - deprecates ``state=get`` in favor of using the module ``gconftool
2_info`` (https://github.com/ansible-collections/community.general/pull/4778).
- lxc_container - the module will no longer make any effort to support Python 2
(https://github.com/ansible-collections/community.general/pull/5304).
- newrelic_deployment - ``appname`` and ``environment`` are no longer valid opti
ons in the v2 API. They will be removed in community.general 7.0.0 (https://gith
ub.com/ansible-collections/community.general/pull/5341).
- proxmox - deprecated the current ``unprivileged`` default value, will be chang ed to ``true`` in community.general 7.0.0 (https://github.com/pull/5224). - proxmox - deprecated the current ``unprivileged`` default value, will be chang ed to ``true`` in community.general 7.0.0 (https://github.com/pull/5224).
- xfconf - deprecated parameter ``disable_facts``, as since version 4.0.0 it onl y allows value ``true`` (https://github.com/ansible-collections/community.genera l/pull/4520).
community.hashi_vault community.hashi_vault
~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
- vault_kv2_get lookup - the ``engine_mount_point option`` in the ``vault_kv2_ge t`` lookup only will change its default from ``kv`` to ``secret`` in community.h ashi_vault version 4.0.0 (https://github.com/ansible-collections/community.hashi _vault/issues/279). - vault_kv2_get lookup - the ``engine_mount_point option`` in the ``vault_kv2_ge t`` lookup only will change its default from ``kv`` to ``secret`` in community.h ashi_vault version 4.0.0 (https://github.com/ansible-collections/community.hashi _vault/issues/279).
 End of changes. 50 change blocks. 
477 lines changed or deleted 552 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)