Warning
In Ansible 2.10, many plugins and modules have migrated to Collections on Ansible Galaxy. Your playbooks should continue to work without any changes. We recommend you start using the fully-qualified collection name (FQCN) in your playbooks as the explicit and authoritative indicator of which collection to use as some collections may contain duplicate module names. You can search the index of all modules to find the collection a module has been relocated to.
This section discusses the behavioral changes between Ansible 2.9 and Ansible 2.10.
It is intended to assist in updating your playbooks, plugins and other parts of your Ansible infrastructure so they will work with this version of Ansible.
We suggest you read this page along with the Ansible Changelog for 2.10 to understand what updates you may need to make.
Since 2.10, Ansible consists of two parts:
The Ansible-base 2.10 Porting Guide is included in this porting guide. The complete list of porting guides can be found at porting guides.
diff: yes- was returning False.ansible_processor_nproc reflects the number of vcpus available to processes (falls back to the number of vcpus available to the scheduler).ansible-galaxy login command has been removed, as the underlying API it used for GitHub auth is being shut down. Publishing roles or collections to Galaxy via ansible-galaxy now requires that a Galaxy API token be passed to the CLI via a token file (default location ~/.ansible/galaxy_token) or (insecurely) via the --token argument to ansible-galaxy.Warning
Links on this page may not point to the most recent versions of modules. We will update them when we can.
0o600 & ~umask when the user did not specify a mode parameter on file-based tasks. This was in response to a CVE report which we have reconsidered. As a result, the mode change has been reverted in 2.10.1, and mode will now default to 0o666 & ~umask as in previous versions of Ansible.mode parameter in all file-based tasks that accept it.dnf and yum - As of version 2.10.1, the dnf module (and yum action when it uses dnf) now correctly validates GPG signatures of packages (CVE-2020-14365). If you see an error such as Failed to validate GPG signature for [package name], please ensure that you have imported the correct GPG key for the DNF repository and/or package you are using. One way to do this is with the rpm_key module. Although we discourage it, in some cases it may be necessary to disable the GPG check. This can be done by explicitly adding disable_gpg_check: yes in your dnf or yum task.add_file_common_args=True added a number of undocumented arguments which were mostly there to ease implementing certain action plugins. The undocumented arguments src, follow, force, content, backup, remote_src, regexp, delimiter, and directory_mode are now no longer added. Modules relying on these options to be added need to specify them by themselves.remote_user’s home directory) when an Ansible module is run. This is to fix becoming an unprivileged user on OpenBSD and to mitigate any attack vector if the current working directory is writable by a malicious user. Install any Python modules needed to run the Ansible modules on the managed node in a system-wide location or in another directory which is in the remote_user’s $PYTHONPATH and readable by the become_user.2.10 lookup plugin names passed in as an argument to the lookup() function were treated as case-insensitive as opposed to lookups invoked via with_<lookup_name>. 2.10 brings consistency to lookup() and with_ to be both case-sensitive.FILE_COMMON_ARGUMENTS have been removed; plugins using these, in particular action plugins, need to be adjusted. The undocumented arguments which were removed are src, follow, force, content, backup, remote_src, regexp, delimiter, and directory_mode._execute_module() whenever possible (eg, ansible.builtin.file rather than file). This ensures that the task’s collection search order is not consulted to resolve the module. Otherwise, a module from a collection earlier in the search path could be used when not intended.No notable changes
frontend_cookie_secret return value now contains a placeholder string instead of the module’s frontend_cookie_secret parameter (https://github.com/ansible-collections/community.general/pull/1736).nxos_bgp and nxos_bgp_neighbor modules in favor of nxos_bgp_global resource module.allowed_ip entry in the allowed_hosts dictionary won’t be allowed after 2.0.0 release.For community.general 2.0.0, the kubevirt modules will be moved to the community.kubevirt collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use kubevirt modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with community.kubevirt. instead of community.general., for example replace community.general.kubevirt_vm in a task by community.kubevirt.kubevirt_vm.
If you use ansible-base and installed community.general manually and rely on the kubevirt modules, you have to make sure to install the community.kubevirt collection as well. If you are using FQCNs, for example community.general.kubevirt_vm instead of kubevirt_vm, it will continue working, but we still recommend to adjust the FQCNs as well.
For community.network 2.0.0, the Cisco NSO modules will be moved to the cisco.nso collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use Cisco NSO modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with cisco.nso. instead of community.network., for example replace community.network.nso_config in a task by cisco.nso.nso_config.
If you use ansible-base and installed community.network manually and rely on the Cisco NSO modules, you have to make sure to install the cisco.nso collection as well. If you are using FQCNs, for example community.network.nso_config instead of nso_config, it will continue working, but we still recommend to adjust the FQCNs as well.
For community.network 2.0.0, the FortiOS modules will be moved to the community.fortios collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use FortiOS modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with community.fortios. instead of community.network., for example replace community.network.fmgr_device in a task by community.fortios.fmgr_device.
If you use ansible-base and installed community.network manually and rely on the FortiOS modules, you have to make sure to install the community.fortios collection as well. If you are using FQCNs, for example community.network.fmgr_device instead of fmgr_device, it will continue working, but we still recommend to adjust the FQCNs as well.
VAULT_ADDR environment variable is now checked last for the url parameter. For details on which use cases are impacted, see (https://github.com/ansible-collections/community.hashi_vault/issues/8).For community.general 2.0.0, the Google modules will be moved to the community.google collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use Google modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with community.google. instead of community.general., for example replace community.general.gcpubsub in a task by community.google.gcpubsub.
If you use ansible-base and installed community.general manually and rely on the Google modules, you have to make sure to install the community.google collection as well. If you are using FQCNs, for example community.general.gcpubsub instead of gcpubsub, it will continue working, but we still recommend to adjust the FQCNs as well.
For community.general 2.0.0, the OC connection plugin will be moved to the community.okd collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use OC connection plugin from this collection, you will need to adjust your playbooks and roles to use FQCNs community.okd.oc instead of community.general.oc.
If you use ansible-base and installed community.general manually and rely on the OC connection plugin, you have to make sure to install the community.okd collection as well. If you are using FQCNs, in other words community.general.oc instead of oc, it will continue working, but we still recommend to adjust this FQCN as well.
For community.general 2.0.0, the hashi_vault lookup plugin will be moved to the community.hashi_vault collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use hashi_vault lookup plugin from this collection, you will need to adjust your playbooks and roles to use FQCNs community.hashi_vault.hashi_vault instead of community.general.hashi_vault.
If you use ansible-base and installed community.general manually and rely on the hashi_vault lookup plugin, you have to make sure to install the community.hashi_vault collection as well. If you are using FQCNs, in other words community.general.hashi_vault instead of hashi_vault, it will continue working, but we still recommend to adjust this FQCN as well.
dns_name option that adds dns_name to the host when True and device has a primary IP address. (#394)status as a group_by option. (398)extracted_primary_ip to allow for config_context or custom_field to overwite. (#377).get instead of .filter. (#376)api_endpoint and token to be found via env. (#391)convert_tags parameter default value will change from False to True to match the collection standard behavior (https://github.com/ansible-collections/community.aws/pull/318).published_ports can contain port mappings next to the special value all, in which case the port mappings are ignored. This behavior is deprecated for community.docker 2.0.0, at which point it will either be forbidden, or this behavior will be properly implemented similar to how the Docker CLI tool handles this (https://github.com/ansible-collections/community.docker/issues/8, https://github.com/ansible-collections/community.docker/pull/60).VAULT_ADDR environment variable for option url will have its precedence lowered in 1.0.0; use ANSIBLE_HASHI_VAULT_ADDR to intentionally override a config value (https://github.com/ansible-collections/community.hashi_vault/issues/8).VAULT_AUTH_METHOD environment variable for option auth_method will be removed in 2.0.0, use ANSIBLE_HASHI_VAULT_AUTH_METHOD instead (https://github.com/ansible-collections/community.hashi_vault/issues/17).VAULT_ROLE_ID environment variable for option role_id will be removed in 2.0.0, use ANSIBLE_HASHI_VAULT_ROLE_ID instead (https://github.com/ansible-collections/community.hashi_vault/issues/20).VAULT_SECRET_ID environment variable for option secret_id will be removed in 2.0.0, use ANSIBLE_HASHI_VAULT_SECRET_ID instead (https://github.com/ansible-collections/community.hashi_vault/issues/20).VAULT_TOKEN_FILE environment variable for option token_file will be removed in 2.0.0, use ANSIBLE_HASHI_VAULT_TOKEN_FILE instead (https://github.com/ansible-collections/community.hashi_vault/issues/15).VAULT_TOKEN_PATH environment variable for option token_path will be removed in 2.0.0, use ANSIBLE_HASHI_VAULT_TOKEN_PATH instead (https://github.com/ansible-collections/community.hashi_vault/issues/15).For community.general 2.0.0, the Hetzner Robot modules will be moved to the community.hrobot collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use Hetzner Robot modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with community.hrobot. instead of community.general.hetzner_, for example replace community.general.hetzner_firewall_info in a task by community.hrobot.firewall_info.
If you use ansible-base and installed community.general manually and rely on the Hetzner Robot modules, you have to make sure to install the community.hrobot collection as well. If you are using FQCNs, i.e. community.general.hetzner_failover_ip instead of hetzner_failover_ip, it will continue working, but we still recommend to adjust the FQCNs as well.
For community.general 2.0.0, the docker modules and plugins will be moved to the community.docker collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use docker content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with community.docker. instead of community.general., for example replace community.general.docker_container in a task by community.docker.docker_container.
If you use ansible-base and installed community.general manually and rely on the docker content, you have to make sure to install the community.docker collection as well. If you are using FQCNs, i.e. community.general.docker_container instead of docker_container, it will continue working, but we still recommend to adjust the FQCNs as well.
For community.general 2.0.0, the postgresql modules and plugins will be moved to the community.postgresql collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use postgresql content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with community.postgresql. instead of community.general., for example replace community.general.postgresql_info in a task by community.postgresql.postgresql_info.
If you use ansible-base and installed community.general manually and rely on the postgresql content, you have to make sure to install the community.postgresql collection as well. If you are using FQCNs, i.e. community.general.postgresql_info instead of postgresql_info, it will continue working, but we still recommend to adjust the FQCNs as well.
For community.network 2.0.0, the routeros modules and plugins will be moved to the community.routeros collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything.
If you use Ansible 2.9 and explicitly use routeros content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with community.routeros. instead of community.network.routeros_, for example replace community.network.routeros_api in a task by community.routeros.api.
If you use ansible-base and installed community.network manually and rely on the routeros content, you have to make sure to install the community.routeros collection as well. If you are using FQCNs, i.e. community.network.routeros_command instead of routeros_command, it will continue working, but we still recommend to adjust the FQCNs as well.
fortimanager httpapi plugin will be removed and replaced by a redirect to the corresponding plugin in the fortios.fortimanager collection. For Ansible 2.10 and ansible-base 2.10 users, this means that it will continue to work assuming that collection is installed. For Ansible 2.9 users, this means that they have to adjust the FQCN from community.network.fortimanager to fortios.fortimanager.fortimanager (https://github.com/ansible-collections/community.network/pull/151).ansible_facts (https://github.com/ansible-collections/community.docker/pull/1).networks_cli_compatible changed to true (https://github.com/ansible-collections/community.docker/pull/1).trust_image_content has been removed (https://github.com/ansible-collections/community.docker/pull/1).state=build has been removed. Use present instead (https://github.com/ansible-collections/community.docker/pull/1).container_limits, dockerfile, http_timeout, nocache, rm, path, buildargs, pull have been removed. Use the corresponding suboptions of build instead (https://github.com/ansible-collections/community.docker/pull/1).force option has been removed. Use the more specific force_* options instead (https://github.com/ansible-collections/community.docker/pull/1).source option is now mandatory (https://github.com/ansible-collections/community.docker/pull/1).use_tls option has been removed. Use tls and validate_certs instead (https://github.com/ansible-collections/community.docker/pull/1).build.pull option changed to false (https://github.com/ansible-collections/community.docker/pull/1).docker_image_info instead (https://github.com/ansible-collections/community.docker/pull/1).ansible_facts (https://github.com/ansible-collections/community.docker/pull/1).ipam_options option has been removed. Use ipam_config instead (https://github.com/ansible-collections/community.docker/pull/1).ansible_facts (https://github.com/ansible-collections/community.docker/pull/1).state=inspect has been removed. Use docker_swarm_info instead (https://github.com/ansible-collections/community.docker/pull/1).constraints option has been removed. Use placement.constraints instead (https://github.com/ansible-collections/community.docker/pull/1).limit_cpu and limit_memory options has been removed. Use the corresponding suboptions in limits instead (https://github.com/ansible-collections/community.docker/pull/1).log_driver and log_driver_options options has been removed. Use the corresponding suboptions in logging instead (https://github.com/ansible-collections/community.docker/pull/1).reserve_cpu and reserve_memory options has been removed. Use the corresponding suboptions in reservations instead (https://github.com/ansible-collections/community.docker/pull/1).restart_policy, restart_policy_attempts, restart_policy_delay and restart_policy_window options has been removed. Use the corresponding suboptions in restart_config instead (https://github.com/ansible-collections/community.docker/pull/1).update_delay, update_parallelism, update_failure_action, update_monitor, update_max_failure_ratio and update_order options has been removed. Use the corresponding suboptions in update_config instead (https://github.com/ansible-collections/community.docker/pull/1).ansible_facts (https://github.com/ansible-collections/community.docker/pull/1).force option has been removed. Use recreate instead (https://github.com/ansible-collections/community.docker/pull/1).liveserver relates to a no longer maintained third-party module for django. It is now deprecated, and will be remove in community.general 3.0.0 (https://github.com/ansible-collections/community.general/pull/1154).proxmox_default_behavior option will change from compatibility to no_defaults in community.general 4.0.0. Set the option to an explicit value to avoid a deprecation warning (https://github.com/ansible-collections/community.general/pull/850).proxmox_default_behavior option will change from compatibility to no_defaults in community.general 4.0.0. Set the option to an explicit value to avoid a deprecation warning (https://github.com/ansible-collections/community.general/pull/850).apply argument (https://github.com/ansible-collections/community.general/pull/360).nxos_interface_ospf in favor of nxos_ospf_interfaces Resource Module.nxos_smu in favour of nxos_rpm module.nxos_ospf_vrf module is deprecated by nxos_ospfv2 and nxos_ospfv3 Resource Modules.pip install --upgrade from ansible-2.9 or earlier to ansible-2.10 or higher. Instead, you must explicitly use pip uninstall ansible before pip installing the new version. If you attempt to upgrade Ansible with pip without first uninstalling, the installer warns you to uninstall first.COLLECTION_INSTALL=$(python -c 'import ansible, os.path ; print("%s/../ansible_collections" % os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p "$COLLECTION_INSTALL".These fortios modules are not automatically redirected from their 2.9.x names to the new 2.10.x names within collections. You must modify your playbooks to use fully qualified collection names for them. You can use the documentation (https://docs.ansible.com/ansible/2.10/collections/fortinet/fortios/) for the fortinet.fortios collection to determine what the fully qualified collection names are.
oif_prefix and oif_source options. These have been superceeded by oif_ps.message is renamed to commit_message since message is used by Ansible Core engine internally.nfs option. This has been superceeded by nfsv3.ansible_date_time.epoch is seconds since EPOCH in UTC to mirror the POSIX facts. The ansible_date_time.epoch_local contains seconds since EPOCH in the local timezone for backwards compatibilityansible_ip_addresses
ansible_processor will now return the index before the other values to match the POSIX fact behaviourfind module.win_find - module has been refactored to better match the behaviour of the find module. Here is what has changed: paths does not exist or is a file, it will no longer fail and will just warn the userislnk, use isjunction to properly report these files. This behaviour matches the win_stat modulesize, this matches the stat and find behaviour and has been removed due to the difficulties in correctly reporting the size of a directorydescription to be case sensitivefullname to be case sensitiverules listdisableRemoteStatusPage response is now remote_status_page_enabled
disable_my_meraki_com response is now local_status_page_enabled
disable_my_meraki has been deprecatedenable_my_meraki is now called local_status_page_enabled
enable_remote_status_page is now called remote_status_page_enabled
enabled response for VLAN status is now vlans_enabled
tags and type now return a listaccess_policy_number is now an int and not a stringtags is now a list and not a stringmessage was renamed to deployment_message since message is used by Ansible Core engine internally.message was renamed to msg, as message is used internally in Ansible Core engine (https://github.com/ansible/ansible/issues/39295)message was renamed to notification_message since message is used by Ansible Core engine internally.Volumes to the Docker daemon. This increases compatibility with the docker CLI program. Note that if you specify volumes: strict in comparisons, this could cause existing containers created with docker_container from Ansible 2.9 or earlier to restart.docker command line utility: a one-port container range combined with a multiple-port host range will no longer result in only the first host port be used, but the whole range being passed to Docker so that a free port in that range will be used.name: * with state: absent will no longer remove every installed package from the system. It is now a noop. (https://github.com/ansible-collections/community.general/pull/569).name: * with state: latest or state: present will no longer install every package from the configured package repositories. Instead, name: *, state: latest will upgrade all already-installed packages, and name: *, state: present is a noop. (https://github.com/ansible-collections/community.general/pull/569).ansible_net_neighbors a list instead of a dict (https://github.com/ansible-collections/community.network/pull/6).datastore_status instead of Ansible internal key results.datacenter option has been removed.host_kernel_status instead of Ansible internal key results.host_ntp_status instead of Ansible internal key results.host_service_status instead of Ansible internal key results.tag_status instead of Ansible internal key results.ip_address and subnet_mask have been removed; use the suboptions ip_address and subnet_mask of the network option instead.*.ps1 file in the directory specified due to it executing potentially unknown scripts. It will follow the default behaviour of only running tests for files that are like *.tests.ps1 which is built into Pester itself.javagateway_pidfile, javagateway_listenip, javagateway_listenport and javagateway_startpollers renamed to zabbix_javagateway_xyz (see UPGRADE.md).ip-addresses key in netbox inventory plugin to ip_addresses (https://github.com/netbox-community/ansible_modules/issues/139)group to tenant_group in netbox_tenant.py (https://github.com/netbox-community/ansible_modules/issues/9)role to prefix_role in netbox_prefix.py (https://github.com/netbox-community/ansible_modules/issues/9)netbox_interface to netbox_device_interface (https://github.com/netbox-community/ansible_modules/issues/9)netbox.netbox.netbox would be used for both inventory plugin and lookup plugin, but in different contexts so no collision will arise, but confusion will. I renamed the lookup plugin to nb_lookup so it will be used with the FQCN netbox.netbox.nb_lookup. The inventory plugin will now be called within an inventory file by netbox.netbox.nb_inventory
To pass in integers via Ansible Jinja filters for a key in data that requires querying an endpoint is now done by making it a dictionary with an id key. The previous behavior was to just pass in an integer and it was converted when normalizing the data, but some people may have names that are all integers and those were being converted erroneously so we made the decision to change the method to convert to an integer for the NetBox API.
tasks:
- name: Create device within NetBox with only required information
netbox_device:
netbox_url: http://netbox-demo.org:32768
netbox_token: 0123456789abcdef0123456789abcdef01234567
data:
name: Test66
device_type:
id: "{{ some_jinja_variable }}"
device_role: Core Switch
site: Test Site
status: Staged
state: present
pynetbox changed to using requests.Session() to manage the HTTP session which broke passing in ssl_verify when building the NetBox API client. This PR makes pynetbox 5.0.4+ the new required version of pynetbox for the Ansible modules and lookup plugin. (https://github.com/netbox-community/ansible_modules/pull/269)All modules were renamed to drop the foreman_ and katello_ prefixes. Additionally to the prefix removal, the following modules were further ranamed:
ansible-test sanity --test yamllint will not be affected by this.collection_name so that deprecation warnings can mention which collection - or ansible-base - is deprecating a feature. This affects all Display.deprecated() or AnsibleModule.deprecate() or Ansible.Basic.Deprecate() calls, and removed_in_version/removed_at_date or deprecated_aliases in module argument specs.default test container for Ansible CollectionsAWSRetry decorator no longer catches NotFound exceptions by default. NotFound exceptions need to be explicitly added using catch_extra_error_codes. Some AWS modules may see an increase in transient failures due to AWS’’s eventual consistency model.network_mode option will be set by default to the name of the first network in networks if at least one network is given and networks_cli_compatible is true (will be default from community.general 2.0.0 on). Set to an explicit value to avoid deprecation warnings if you specify networks and set networks_cli_compatible to true. The current default (not specifying it) is equivalent to the value default.container_default_behavior, whose default value will change from compatibility to no_defaults. Set to an explicit value to avoid deprecation warnings.name, email and password arguments when state=absent.pureuser account password on a FlashBladecheck_invalid_arguments in AnsibleModule, AzureModule and UTMModule.get_md55 option and md5 return value.letsencrypt module has been removed. Use acme_certificate instead.cyberark.conjur collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/570).check_invalid_arguments in UTMModule.community.digitalocean collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/622).infinidat.infinibox collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/607).community.mysql collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/633).recurse option, use extra_args=--recursive insteadcommunity.proxysql collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/624).datacenter optionip_address option; use sub-option ip_address in the network option insteadsubnet_mask option; use sub-option subnet_mask in the network option insteadmount_path in favour of mount_paths.extra_opts option.hash_behaviour for future removal.aws_access_key, aws_secret_key and security_token will be made mutually exclusive with profile after 2022-06-01.template_format option had no effect since Ansible 2.3 and will be removed after 2022-06-01template_format option has been deprecated and will be removed in a later release. It has been ignored by the module since Ansible 2.3.version option had no effect and will be removed in after 2022-06-01group and group_id options will become mutually exclusive. Currently group_id is ignored if you pass both.no_device alias NoDevice has been deprecated and will be removed after 2022-06-01virtual_name alias VirtualName has been deprecated and will be removed after 2022-06-01wait_timeout option had no effect and will be removed after 2022-06-01wait_timeout option had no effect and will be removed after 2022-06-01wait option had no effect and will be removed after 2022-06-01wait_timeout option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.5.wait option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.5.associate_public_ip_address option had no effect and will be removed after 2022-06-01list option in favor of ec2_tag_infolist as a state has been deprecated and will be removed in a later release. The ec2_tag_info can be used to fetch the tags on an EC2 resource.log_path option. This option will be removed in a major release after 2022-07-01.log_path option has been deprecated and will be removed in a later release. This was undocumented and only related to debugging information for module development.ensure alias for the state option has been deprecated and will be removed in a later release. Please use state instead of ensure.productid alias for the product_id option has been deprecated and will be removed in a later release. Please use product_id instead of productid.username and password options has been deprecated and will be removed in a later release. The same functionality can be done by using become: yes and become_flags: logon_type=new_credentials logon_flags=netcredentials_only on the task.2021-07-01.template_format option had no effect since Ansible 2.3 and will be removed after 2022-06-01version option had no effect and will be removed after 2022-06-01version option has been deprecated and will be removed in a later release. It has always been ignored by the module.wait_timeout option had no effect and will be removed after 2022-06-01wait_timeout option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.3.wait_timeout option had no effect and will be removed after 2022-06-01wait option had no effect and will be removed after 2022-06-01associate_public_ip_address option had no effect and will be removed after 2022-06-01associate_public_ip_address option has been deprecated and will be removed after a later release. It has always been ignored by the module.state option has been deprecated and will change from absent to present after 2022-06-01state option will change from absent to present. To maintain the existing behavior explicitly set state to absent.fail_on_delete option had no effect and will be removed after 2022-06-01fail_on_delete option has been deprecated and will be removed after a later release. It has always been ignored by the module.policy_document will be removed after 2022-06-01. To maintain the existing behavior use the policy_json option and read the file with the lookup plugin.skip_duplicates will change after 2022-06-01 from true to false.skip_duplicates option will change from true to false. To maintain the existing behavior explicitly set it to true.policy_document option has been deprecated and will be removed after a later release. To maintain the existing behavior use the policy_json option and read the file with the lookup plugin.purge_policies option (also know as purge_policy) default value will change from true to false
requester_pays option had no effect and will be removed after 2022-06-01requester_pays option has been deprecated and will be removed after a later release. It has always been ignored by the module.retries option had no effect and will be removed after 2022-06-01retries option has been deprecated and will be removed after 2022-06-01. It has always been ignored by the module.version option except 1 are deprecated. The value 1 denotes the current only standardized CSR version.token parameter and v2 api deploys. This feature will be removed in community.general 3.0.0.wait option had no effect and will be removed in community.general 3.0.0.wait parameter will be removed. It has always been ignored by the module.trust_image_content option is now deprecated and will be removed in community.general 3.0.0. It has never been used by the module.trust_image_content option will be removed. It has always been ignored by the module.container_default_behavior will change from compatibility to no_defaults in community.general 3.0.0. Set the option to an explicit value to avoid a deprecation warning.network_mode will change in community.general 3.0.0, provided at least one network is specified and networks_cli_compatible is true. See porting guide, module documentation or deprecation warning for more details.out and err have been deprecated and will be removed in community.general 3.0.0. Use stdout and stderr instead.err and out have been deprecated. Use stdout and stderr from now on instead.helm module to deprecated. New implementation is available in community.kubernetes collection.bios_attribute_name and bios_attribute_value in favor of new bios_attributes` option.bios_attribute_name and bios_attribute_value options will be removed. To maintain the existing behavior use the bios_attributes option instead.resource_id option to specify target resource to modify.resource_id option to specify target resource to modify.force option never had any effect. It is now deprecated, and will be removed in 3.0.0 (https://github.com/ansible-collections/community.general/pull/568).tag_facts since it does not return multiple tags with the same name and different category id. To maintain the existing behavior use tag_info which is a list of tag metadata.interface sub-options type and main when proxy type is set to passive via status=passive. Make sure these suboptions are removed from your playbook as they were never supported by Zabbix in the first place.
© 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.11/porting_guides/porting_guide_2.10.html