Ansible 5 is based on Ansible-core 2.12.
We suggest you read this page along with the Ansible 5 Changelog to understand what updates you may need to make.
async, setting ANSIBLE_ASYNC_DIR under environment: is no longer valid. Instead, use the shell configuration variable async_dir, for example by setting ansible_async_dir:tasks:
- dnf:
name: '*'
state: latest
async: 300
poll: 5
vars:
ansible_async_dir: /path/to/my/custom/dir
undef() function is added to the templating environment for creating undefined variables directly in a template. Optionally, a hint may be provided for variables which are intended to be overridden.vars:
old: "{{ undef }}"
new: "{{ undef() }}"
new_with_hint: "{{ undef(hint='You must override this variable') }}"
The default value of INTERPRETER_PYTHON changed to auto. The list of Python interpreters in INTERPRETER_PYTHON_FALLBACK changed to prefer Python 3 over Python 2. The combination of these two changes means the new default behavior is to quietly prefer Python 3 over Python 2 on remote hosts. Previously a deprecation warning was issued in situations where interpreter discovery would have used Python 3 but the interpreter was set to /usr/bin/python.
INTERPRETER_PYTHON_FALLBACK can be changed from the default list of interpreters by setting the ansible_interpreter_python_fallback variable.
See interpreter discovery documentation for more details.
ansible-vault no longer supports PyCrypto and requires cryptography.ansible-core 2.13 will remove support for Python 2.6.when conditionals no longer automatically parse string booleans such as "true" and "false" into actual booleans. Any variable containing a non-empty string is considered true. This was previously configurable with the CONDITIONAL_BARE_VARS configuration option (and the ANSIBLE_CONDITIONAL_BARE_VARS environment variable). This setting no longer has any effect. Users can work around the issue by using the |bool filter:vars:
teardown: 'false'
tasks:
- include_tasks: teardown.yml
when: teardown | bool
- include_tasks: provision.yml
when: not teardown | bool
_remote_checksum() method in ActionBase is deprecated. Any action plugin using this method should use _execute_remote_stat() instead.cron now requires name to be specified in all cases.cron no longer allows a reboot parameter. Use special_time: reboot instead.hostname - On FreeBSD, the before result will no longer be "temporarystub" if permanent hostname file does not exist. It will instead be "" (empty string) for consistency with other systems.hostname - On OpenRC and Solaris based systems, the before result will no longer be "UNKNOWN" if the permanent hostname file does not exist. It will instead be "" (empty string) for consistency with other systems.pip now uses the pip Python module installed for the Ansible module’s Python interpreter, if available, unless executable or virtualenv were specified.The following modules no longer exist:
No notable changes
No notable changes
unique filter with Jinja2 < 2.10 is case-sensitive and now raise coherently an error if case_sensitive=False instead of when case_sensitive=True.intersect, difference, symmetric_difference and union) are now case-sensitive. Explicitly use case_sensitive=False to keep previous behavior. Note: with Jinja2 < 2.10, the filters were already case-sensitive by default.password_hash now uses passlib defaults when an option is unspecified, for example bcrypt_sha256, now default to the “2b” format and if the “2a” format is required it must be specified.No notable changes
No notable changes
community.sap has been renamed to community.sap_libs. For now both collections are included in Ansible. The content in community.sap will be replaced with deprecated redirects to the new collection in Ansible 7.0.0, and these redirects will eventually be removed from Ansible. Please update your FQCNs for community.sap.tls_hostname that was supposed to be removed in community.docker 2.0.0 will now be removed in version 3.0.0 (https://github.com/ansible-collections/community.docker/pull/362).out and err that were supposed to be removed in community.docker 2.0.0 will now be removed in version 3.0.0 (https://github.com/ansible-collections/community.docker/pull/362).disks parameter has changed.vm_home.Ansible 2.9 and ansible-base 2.10. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing against Ansible 2.9 and ansible-base 2.10. Both will very soon be End of Life and if you are still using them, you should consider upgrading to the latest Ansible / ansible-core 2.11 or later as soon as possible (https://github.com/ansible-collections/community.mysql/pull/343).Ansible 2.9 and ansible-base 2.10. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing against Ansible 2.9 and ansible-base 2.10. Both will very soon be End of Life and if you are still using them, you should consider upgrading to the latest Ansible / ansible-core 2.11 or later as soon as possible (https://github.com/ansible-collections/community.postgresql/pull/245).token_validate will change its default from True to False in community.hashi_vault version 4.0.0. The vault_login lookup and module will keep the default value of True (https://github.com/ansible-collections/community.hashi_vault/issues/248).upgrade state.priv argument has been deprecated and will be removed in community.postgresql 3.0.0. Please use the postgresql_privs module to grant/revoke privileges instead (https://github.com/ansible-collections/community.postgresql/issues/212).false in community.general 7.0.0, as this is also the default in nmcli (https://github.com/ansible-collections/community.general/pull/4334).true of the want_proxmox_nodes_ansible_host option has been deprecated. The default will change to false in community.general 6.0.0. To keep the current behavior, explicitly set want_proxmox_nodes_ansible_host to true in your inventory configuration. We suggest to already switch to the new behavior by explicitly setting it to false, and by using compose: to set ansible_host to the correct value. See the examples in the plugin documentation for details (https://github.com/ansible-collections/community.general/pull/4466).update_cache cannot differentiate between up to date and outdated package lists and will report changed in both situations (https://github.com/ansible-collections/community.general/pull/4318).executable parameter must support --print-format in order to be used by this module. In particular, AUR helper yay is known not to currently support it (https://github.com/ansible-collections/community.general/pull/4312).changed status of update_cache will no longer be ignored if name or upgrade is specified. To keep the old behavior, add something like register: result and changed_when: result.packages | length > 0 to your task (https://github.com/ansible-collections/community.general/pull/4329).ios_acls - Deprecated fragment attribute added boolean alternate as enable_fragment.sender is deprecated and will be disallowed in community.general 6.0.0 (https://github.com/ansible-collections/community.general/pull/4140).unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress. Wait for the job to complete and run the task again.Successfully updated the local access setting if an unsupported value is provided for the parameter timeout_limit. However, this value is not actually applied on OpenManage Enterprise Modular.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.
max_login and lockout have been set there is currently no way to rest these to zero except through the FlashArray GUIunable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress. Wait for the job to complete and run the task again.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.
ModuleHelper.VarDict (https://github.com/ansible-collections/community.general/pull/3801).aws_iam_login method has been renamed to aws_iam. The old name will be removed in collection version 3.0.0. Until then both names will work, and a warning will be displayed when using the old name (https://github.com/ansible-collections/community.hashi_vault/pull/193).unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress. Wait for the job to complete and run the task again.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.
aws, azure, cs, hcloud, nios, opennebula, openshift and vcenter. Collections should instead use one of the supported integration test requirements files, such as the tests/integration/requirements.txt file.ansible-test shell command. Only the integration and windows-integration commands provide HTTP Tester.--disable-httptester option is no longer available. The HTTP Tester is no longer optional for tests that specify it.--httptester option is no longer available. To override the container used for HTTP Tester tests, set the ANSIBLE_HTTP_TEST_CONTAINER environment variable instead.modules and module_utils are now limited to importing only ansible.module_utils from the ansible module.when conditionals no longer automatically parse string booleans such as "true" and "false" into actual booleans. Any non-empty string is now considered true. The CONDITIONAL_BARE_VARS configuration variable no longer has any effect.with open() to simplify exception handling code which leaked file handles in several spotstemporarystub no longer gets written to the hostname file in the get methods (and in check_mode). As a result, the default hostname will now appear as '' (empty string) instead of temporarystub for consistency with other strategies. This means the before result will be different.before value will now be '' (empty string) if the permanent hostname file does not exist, for consistency with other strategies.case_sensitive=False as the Ansible’s fallback is case-sensitive (https://github.com/ansible/ansible/pull/74256)OK when launching a new instance, the action will need to specify state: started (https://github.com/ansible-collections/amazon.aws/pull/481).attachment_set is now a list of attachments with Multi-Attach support on disk. (https://github.com/ansible-collections/amazon.aws/pull/362).purge_tags option has been added, which defaults to True. (https://github.com/ansible-collections/amazon.aws/pull/252)scrub_none_parameters function so that descend_into_lists is set to True by default (https://github.com/ansible-collections/amazon.aws/pull/297).amazon.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_instance.amazon.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_instance_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_endpoint.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_endpoint_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_endpoint_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_endpoint_service_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_igw.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_igw_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_igw_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_nat_gateway.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_nat_gateway_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_nat_gateway_info.kms_keys attribute rather than the keys attribute (https://github.com/ansible-collections/community.aws/pull/648).dirName text parsing and to text converting code to conform to Sections 2 and 3 of RFC 4514. This is similar to how cryptography handles this (https://github.com/ansible-collections/community.crypto/pull/274).ipaddress. If you are using Python 2.x, please make sure to install the library (https://github.com/ansible-collections/community.crypto/pull/287).ipaddress (https://github.com/ansible-collections/community.crypto/pull/287).cryptography version used, the modules might not return the ASN.1 value for an extension as contained in the certificate respectively CSR, but a re-encoded version of it. This should usually be identical to the value contained in the source file, unless the value was malformed. For extensions not handled by C(cryptography) the value contained in the source file is always returned unaltered (https://github.com/ansible-collections/community.crypto/pull/318).subject respectively issuer fields no longer ignore empty values, but instead fail when encountering them (https://github.com/ansible-collections/community.crypto/pull/316).check_consistency=true (https://github.com/ansible-collections/community.crypto/pull/309).issuer order is ignored. If order is important, use the new issuer_ordered option (https://github.com/ansible-collections/community.crypto/pull/316).txt_transformation=api (https://github.com/ansible-collections/community.dns/issues/48, https://github.com/ansible-collections/community.dns/pull/57, https://github.com/ansible-collections/community.dns/pull/60).ModuleOptionProvider object instead of an AnsibleModule object. Alternatively an Ansible plugin instance can be passed (https://github.com/ansible-collections/community.dns/pull/37).bulk_apply_changes) now also returns the records that were deleted, created or updated (https://github.com/ansible-collections/community.dns/pull/63).none is now accepted and returned in this case (https://github.com/ansible-collections/community.dns/pull/52, https://github.com/ansible-collections/community.dns/issues/50).overwrite was replaced by a new option on_existing. Specifying overwrite=true is equivalent to on_existing=replace (the new default). Specifying overwrite=false with state=present is equivalent to on_existing=keep_and_fail, and specifying overwrite=false with state=absent is equivalent to on_existing=keep (https://github.com/ansible-collections/community.dns/pull/31).timeout defaulting behavior so that stop_grace_period, if defined in the compose file, will be used if timeout` is not specified (https://github.com/ansible-collections/community.docker/pull/163).destination file (https://github.com/ansible-collections/community.general/pull/3075).ipaddress installed from pypi (https://github.com/ansible-collections/community.general/pull/2441).ipaddress installed from pypi (https://github.com/ansible-collections/community.general/pull/2441).url option (the Vault address), so a value must be supplied (https://github.com/ansible-collections/community.hashi_vault/issues/83).failure: already have such address), you need to adjust your roles/playbooks. We suggest to use failed_when to accept failure in specific circumstances, for example failed_when: "'failure: already have ' in result.msg[0]" (https://github.com/ansible-collections/community.routeros/pull/39).changed_when to determine the correct changed status for a task (https://github.com/ansible-collections/community.routeros/pull/50).release_namespace parameter (https://github.com/ansible-collections/kubernetes.core/pull/85).release_namespace parameter (https://github.com/ansible-collections/kubernetes.core/pull/85).nac_sg_* to na_sg_*. Playbooks and Roles must be updated to match.--remote option was inconsistent.integration command can now be executed on two separate hosts instead of always running on the controller. The target host can be one provided by ansible-test or by the user, as long as it is accessible using SSH.docker pointing to podman was required.--controller and --target / --target-python options have been added to allow more control over test environments.ansible-test, thus matching the Ansible controller Python requirements. Older Python versions (2.6 - 2.7 and 3.5 - 3.10) can still be the target for relevant tests.import and compile are controller tests. The controller tests always run using the same Python version used to run ansible-test. The target tests use the Python version(s) specified by the user, or all available Python versions.centos6 and default test containers now use a PyPI proxy container to access PyPI when Python 2.6 is used. This allows tests running under Python 2.6 to continue functioning even though PyPI is discontinuing support for non-SNI capable clients.future-import-boilerplate and metaclass-boilerplate sanity tests are limited to remote-only code. Additionally, they are skipped for collections which declare no support for Python 2.x.import and compile sanity tests limit remote-only Python version checks to remote-only code.junit_xml and ordereddict Python modules are no longer required to use the junit callback plugin.botocore<1.18.0 and boto3<1.15.0. Most modules will continue to work with older versions of the AWS SDK, however compatibility with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/amazon.aws/pull/502).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_instance.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_instance_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_endpoint.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_endpoint_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_endpoint_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_endpoint_service_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_igw.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_igw_facts.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_igw_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_nat_gateway.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_nat_gateway_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_nat_gateway_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_route_table.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_route_table_facts.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.ec2_vpc_route_table_info.ise_uses_api_gateway to module options.botocore<1.18.0 and boto3<1.15.0 (https://github.com/ansible-collections/community.aws/pull/711). Most modules will continue to work with older versions of the AWS SDK, however compatibility with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/amazon.aws/pull/442).client_id is no longer marked as no_log=true. If you relied on its value not showing up in logs and output, please mark the whole tasks with no_log: true (https://github.com/ansible-collections/community.general/pull/2045).community.kubernetes to kubernetes.core (https://github.com/ansible-collections/community.kubernetes/pull/425).as_single_query option will be changed to yes in community.postgresql 2.0.0 (https://github.com/ansible-collections/community.postgresql/issues/85).fortios_configuration_fact to use multiple selectors concurrently.check_mode in all cofigurationAPI-based modules.fortios_configuration_fact and fortios_monitor_fact.firewall_central_snat_map.fortios_monitor_fact and fortios_log_fact.ansible.module_utils.common.removed was previously deprecated and has been removed.shutdown_timeout and shutdown_timeout_sec which has not done anything since Ansible 2.5.acme_directory option is now required (https://github.com/ansible-collections/community.crypto/pull/290).acme_version option is now required (https://github.com/ansible-collections/community.crypto/pull/290).retrieve_orders=url_list no longer returns the return value orders. Use the order_uris return value instead (https://github.com/ansible-collections/community.crypto/pull/290).crypto.pem instead (https://github.com/ansible-collections/community.crypto/pull/290).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).version now only accepts the (default) value 1 (https://github.com/ansible-collections/community.crypto/pull/290).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).assertonly provider (https://github.com/ansible-collections/community.crypto/pull/289).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).pyopenssl backend (https://github.com/ansible-collections/community.crypto/pull/273).container_default_behavior changed to no_defaults (https://github.com/ansible-collections/community.docker/pull/210).network_mode is now the name of the first network specified in networks if such are specified and networks_cli_compatible=true (https://github.com/ansible-collections/community.docker/pull/210).all can no longer be used in published_ports next to other values. Please use publish_all_ports=true instead (https://github.com/ansible-collections/community.docker/pull/210).email option (https://github.com/ansible-collections/community.docker/pull/210).infoblox.nios_modules collection to continue using these plugins and modules, and update your FQCNs (https://github.com/ansible-collections/community.general/pull/3592).ipaddress has been removed. Please use ipaddress from the Python 3 standard library, or from pypi. (https://github.com/ansible-collections/community.general/pull/2441).system_lib option. Use Ansible’s privilege escalation mechanism instead; the option basically used sudo (https://github.com/ansible-collections/community.general/pull/3461).message of the message_content option (https://github.com/ansible-collections/community.general/pull/3461).proxmox_default_behavior changed to no_defaults (https://github.com/ansible-collections/community.general/pull/3461).proxmox_default_behavior changed to no_defaults (https://github.com/ansible-collections/community.general/pull/3461).dist option which was not used by the module (https://github.com/ansible-collections/community.general/pull/3461).msg, msg_format and chat_id options (https://github.com/ansible-collections/community.general/pull/3461).disable_facts changed to true, and the value false is no longer allowed. Register the module results instead (https://github.com/ansible-collections/community.general/pull/3461).VAULT_AUTH_METHOD, VAULT_TOKEN_PATH, VAULT_TOKEN_FILE, VAULT_ROLE_ID, VAULT_SECRET_ID (https://github.com/ansible-collections/community.hashi_vault/pull/173).--docker-no-pull option is deprecated and has no effect.--no-pip-check option is deprecated and has no effect.ec2 module has been deprecated in favour of the boto3 based ec2_instance module. The ec2 module will be removed in release 4.0.0 (https://github.com/ansible-collections/amazon.aws/pull/424).ec2_elb fact has been deprecated and will be removed in release 4.0.0 of the collection. The module now returns elb which can be accessed using the register keyword (https://github.com/ansible-collections/amazon.aws/pull/552).new_config return key has been deprecated and will be removed in a future release. It will be replaced by dhcp_config. Both values are returned in the interim. (https://github.com/ansible-collections/amazon.aws/pull/252)look_for_keys was set automatically based on the values of the password and private_key_file options passed to network_cli. This option can now be set explicitly, and the automatic setting of look_for_keys will be removed after 2024-01-01 (https://github.com/ansible-collections/ansible.netcommon/pull/271).ignore_errors: True, this ability will be removed in a future version. Use ignore_unreachable: True to ignore unreachable hosts instead. - https://github.com/ansible-collections/ansible.windows/issues/62
filtered_reason return value for each filtered up in favour of filtered_reasons. This has been done to show all the reasons why an update was filtered and not just the first reason.use_scheduled_task option as it is no longer used.whitelist and blacklist options in favour of accept_list and reject_list respectively to conform to the new standards used in Ansible for these types of options.nxos_ntp, nxos_ntp_options, nxos_ntp_auth modules.ALL index. Passing includes for such indexes is currently ignored but will result in failures after version 3.0.0 (https://github.com/ansible-collections/community.aws/pull/726).ec2_elb module has been removed and redirected to the elb_instance module which functions identically. The original ec2_elb name is now deprecated and will be removed in release 3.0.0 (https://github.com/ansible-collections/community.aws/pull/586).ec2_elb_info module has been deprecated in favour of the boto3 based elb_classic_lb_info module. The ec2_elb_info module will be removed in release 3.0.0 (https://github.com/ansible-collections/community.aws/pull/586).elb_classic_lb module has been removed and redirected to the amazon.aws.ec2_elb_lb module which functions identically.ec2_elb fact has been deprecated and will be removed in release 4.0.0 of the collection. See the module documentation for an alternative example using the register keyword (https://github.com/ansible-collections/community.aws/pull/773).iam module has been deprecated in favour of the boto3 based iam_user, iam_group and iam_role modules. The iam module will be removed in release 3.0.0 (https://github.com/ansible-collections/community.aws/pull/664).cert, chain_cert and key parameters has been deprecated. We recommend using a lookup plugin to read the files instead, see the documentation for an example (https://github.com/ansible-collections/community.aws/pull/735).dup_ok parameter is currently false, in version 4.0.0 this will be updated to true. To preserve the current behaviour explicitly set the dup_ok parameter to false (https://github.com/ansible-collections/community.aws/pull/737).rds module has been deprecated in favour of the boto3 based rds_instance module. The rds module will be removed in release 3.0.0 (https://github.com/ansible-collections/community.aws/pull/663).amazon.aws.ec2 inventory plugin.docker_swarm connection plugin and docker_compose and docker_stack*` modules - the current default ``localhost for tls_hostname is deprecated. In community.docker 2.0.0 it will be computed from docker_host instead (https://github.com/ansible-collections/community.docker/pull/134).command_handling’s default value, compatibility, is deprecated and will change to correct in community.docker 3.0.0. A deprecation warning is emitted by the module in cases where the behavior will change. Please note that ansible-core will output a deprecation warning only once, so if it is shown for an earlier task, there could be more tasks with this warning where it is not shown (https://github.com/ansible-collections/community.docker/pull/186).all in published_ports has been deprecated. Use publish_all_ports=true instead (https://github.com/ansible-collections/community.docker/pull/210).availability_zone and instance_names (https://github.com/ansible-collections/community.general/issues/2429).username options have been deprecated in favor of workspace and will be removed in community.general 6.0.0 (https://github.com/ansible-collections/community.general/pull/2045).gitlab_group to name or path is deprecated. Use full_path instead (https://github.com/ansible-collections/community.general/pull/3451).flow is now deprecated and will be removed in community.general 6.0.0; use end_state instead (https://github.com/ansible-collections/community.general/pull/3280).group is now deprecated and will be removed in community.general 6.0.0; use end_state instead (https://github.com/ansible-collections/community.general/pull/3280).backupsenabled is deprecated and will be removed in community.general 5.0.0 (https://github.com/ansible-collections/community.general/pull/2410).true of ignore_volatile_options is deprecated and will change to false in community.general 6.0.0 (https://github.com/ansible-collections/community.general/pull/3429).functions because it was not used in the code (https://github.com/ansible-collections/community.general/pull/2845).get state. The new module xfconf_info should be used instead (https://github.com/ansible-collections/community.general/pull/3049).2.0.0 of community.hashi_vault (https://github.com/ansible-collections/community.hashi_vault/issues/81).2.0.0 of community.hashi_vault (https://github.com/ansible-collections/community.hashi_vault/issues/81).[lookup_hashi_vault] section in the ansible.cfg file is deprecated and will be removed in collection version 3.0.0. Instead, the section [hashi_vault_collection] can be used, which will apply to all plugins in the collection going forward (https://github.com/ansible-collections/community.hashi_vault/pull/144).community.kubernetes collection is being renamed to kubernetes.core. All content in the collection has been replaced by deprecated redirects to kubernetes.core. If you are using FQCNs starting with community.kubernetes, please update them to kubernetes.core (https://github.com/ansible-collections/community.kubernetes/pull/439).
© 2012–2018 Michael DeHaan
© 2018–2025 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_5.html