Ansible 9 is based on Ansible-core 2.16.
We suggest you read this page along with the Ansible 9 Changelog to understand what updates you may need to make.
Conditionals - due to mitigation of security issue CVE-2023-5764 in ansible-core 2.16.1, conditional expressions with embedded template blocks can fail with the message “Conditional is marked as unsafe, and cannot be evaluated.” when an embedded template consults data from untrusted sources like module results or vars marked !unsafe. Conditionals with embedded templates can be a source of malicious template injection when referencing untrusted data, and can nearly always be rewritten without embedded templates. Playbook task conditional keywords such as when and until have long displayed warnings discouraging use of embedded templates in conditionals; this warning has been expanded to non-task conditionals as well, such as the assert action.
- name: task with a module result (always untrusted by Ansible)
shell: echo "hi mom"
register: untrusted_result
# don't do it this way...
# - name: insecure conditional with embedded template consulting untrusted data
# assert:
# that: '"hi mom" is in {{ untrusted_result.stdout }}'
- name: securely access untrusted values directly as Jinja variables instead
assert:
that: '"hi mom" is in untrusted_result.stdout'
community.network collection has been deprecated. It will be removed from Ansible 12 if no one starts maintaining it again before Ansible 12. See Collections Removal Process for unmaintained collections for more details (https://forum.ansible.com/t/8030).ngine_io.exoscale collection has been deprecated. It will be removed from Ansible 11 if no one starts maintaining it again before Ansible 11. See Collections Removal Process for unmaintained collections for more details (https://forum.ansible.com/t/2572).users_info filter returned variable plugin_auth_string contains the hashed password and it’s misleading, it will be removed from community.mysql 4.0.0. Use the plugin_hash_string return value instead (https://github.com/ansible-collections/community.mysql/pull/629).user alias of the name argument has been deprecated and will be removed in collection version 5.0.0. Use the name argument instead.frr.frr collection has been deprecated. It will be removed from Ansible 11 if no one starts maintaining it again before Ansible 11. See Collections Removal Process for unmaintained collections for more details (https://forum.ansible.com/t/6243).openvswitch.openvswitch collection has been deprecated. It will be removed from Ansible 11 if no one starts maintaining it again before Ansible 11. See Collections Removal Process for unmaintained collections for more details (https://forum.ansible.com/t/6245).crypt standard library module (https://github.com/ansible-collections/community.general/issues/4691, https://github.com/ansible-collections/community.general/pull/8497).crypt standard library module (https://github.com/ansible-collections/community.general/issues/4690, https://github.com/ansible-collections/community.general/pull/8497).message argument in grafana_dashboard
Please note that the fix for requests 2.32.0 included in community.docker 3.10.1 only fixes problems with the vendored Docker SDK for Python code. Modules and plugins that use Docker SDK for Python can still fail due to the SDK currently being incompatible with requests 2.32.0.
If you still experience problems with requests 2.32.0, such as error messages like Not supported URL scheme http+docker, please restrict requests to <2.32.0.
template parameter has been deprecated and will be removed in a release after 2026-05-01. The template_body parameter can be used in conjungtion with the lookup plugin (https://github.com/ansible-collections/amazon.aws/pull/2048).boto3 parameter for get_aws_connection_info() will be removed in a release after 2025-05-01. The boto3 parameter has been ignored since release 4.0.0 (https://github.com/ansible-collections/amazon.aws/pull/2047).boto3 parameter for get_aws_region() will be removed in a release after 2025-05-01. The boto3 parameter has been ignored since release 4.0.0 (https://github.com/ansible-collections/amazon.aws/pull/2047).boto3 parameter for get_ec2_security_group_ids_from_names() will be removed in a release after 2025-05-01. The boto3 parameter has been ignored since release 4.0.0 (https://github.com/ansible-collections/amazon.aws/pull/2047).community.crypto.acme[.documentation] docs fragment is deprecated and will be removed from community.crypto 3.0.0. Replace it with both the new community.crypto.acme.basic and community.crypto.acme.account fragments (https://github.com/ansible-collections/community.crypto/pull/735).get_cert_information() method for a ACME crypto backend must be implemented from community.crypto 3.0.0 on (https://github.com/ansible-collections/community.crypto/pull/736).crypto.module_backends.common module utils is deprecated and will be removed from community.crypto 3.0.0. Use the improved argspec module util instead (https://github.com/ansible-collections/community.crypto/pull/749).community.docker.docker_compose_v2 module, which works with Docker Compose v2 (https://github.com/ansible-collections/community.docker/issues/823, https://github.com/ansible-collections/community.docker/pull/833).ssl_version option has been deprecated and will be removed from community.docker 4.0.0. It has already been removed from Docker SDK for Python 7.0.0, and was only necessary in the past to work around SSL/TLS issues (https://github.com/ansible-collections/community.docker/pull/853).CryptoBackend must override get_ordered_csr_identifiers(). The current default implementation, which simply sorts the result of get_csr_identifiers(), will then be removed (https://github.com/ansible-collections/community.crypto/pull/725).vm_tools_install_status will be removed from next major version (5.0.0) of the collection since the API call that provides this information has been deprecated by VMware. Use vm_tools_running_status / vm_tools_version_status instead (https://github.com/ansible-collections/community.vmware/issues/2033)./ (https://github.com/ansible-collections/amazon.aws/pull/1998).inspur.sm collection is considered unmaintained and will be removed from Ansible 11 if no one starts maintaining it again before Ansible 11. See Collections Removal Process for unmaintained collections for more details, including for how this can be cancelled (https://forum.ansible.com/t/2854).netapp.storagegrid collection is considered unmaintained and will be removed from Ansible 11 if no one starts maintaining it again before Ansible 11. See Collections Removal Process for unmaintained collections for more details, including for how this can be cancelled (https://forum.ansible.com/t/2811).purestorage.fusion collection has been deprecated. It will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See Collections Removal Process for unmaintained collections for more details (https://forum.ansible.com/t/3712)._pipe: if the object needs to be (re-)generated, only the changed status is set, but the object is not updated. From community.crypto 3.0.0 on, the modules will ignore check mode and always act as if check mode is not active. This behavior can already achieved now by adding check_mode: false to the task. If you think this breaks your use-case of this module, please create an issue in the community.crypto repository (https://github.com/ansible-collections/community.crypto/issues/712, https://github.com/ansible-collections/community.crypto/pull/714).ome_network_attributes, then this module does not provide a correct error message.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.
community.docker collection now depends on the community.library_inventory_filtering_v1 collection. This utility collection provides host filtering functionality for inventory plugins. If you use the Ansible community package, both collections are included and you do not have to do anything special. If you install the collection with ansible-galaxy collection install, it will be installed automatically. If you install the collection by copying the files of the collection to a place where ansible-core can find it, for example by cloning the git repository, you need to make sure that you also have to install the dependency if you are using the inventory plugins (https://github.com/ansible-collections/community.docker/pull/698).requests package which is required by hvac now has a more restrictive range for this collection in certain use cases due to breaking security changes in ansible-core that were backported (https://github.com/ansible-collections/community.hashi_vault/pull/416).OME_USERNAME and OME_PASSWORD as fallback for credentials.IDRAC_USERNAME and IDRAC_PASSWORD as fallback for credentials.CUSTOMCERTIFICATE.filters option has been renamed to simple_filters. The old name will stop working in community.hrobot 2.0.0 (https://github.com/ansible-collections/community.dns/pull/181).ignore for the image_name_mismatch parameter has been deprecated and will switch to recreate in community.docker 4.0.0. A deprecation warning will be printed in situations where the default value is used and where a behavior would change once the default changes (https://github.com/ansible-collections/community.docker/pull/703).consul_token and consul_policy can be used instead (https://github.com/ansible-collections/community.general/pull/7901).filters option has been renamed to simple_filters. The old name will stop working in community.hrobot 2.0.0 (https://github.com/ansible-collections/community.hrobot/pull/94).ome_network_attributes, then this module does not provide a correct error message.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.
pep8 sanity test is unable to detect f-string spacing issues (E201, E202) on Python 3.10 and 3.11. They are correctly detected under Python 3.12. See (https://github.com/PyCQA/pycodestyle/issues/1190).ome_network_attributes, then this module does not provide a correct error message.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.
cli entry to use the timeout from the command line, will see the value change if the use had configured it in any of the lower precedence methods. If relying on this behaviour to consume the global/generic timeout from the DEFAULT_TIMEOUT constant, please consult the documentation on plugin configuration to add the overlaping entries.botocore<1.29.0 and boto3<1.26.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/amazon.aws/pull/1763).module_utils.urls was previously deprecated and has been removed (https://github.com/ansible-collections/amazon.aws/pull/1540).botocore<1.29.0 and boto3<1.26.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/amazon.aws/pull/1763).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.aws_region_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.aws_s3_bucket_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_access_key.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_access_key_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_group (https://github.com/ansible-collections/community.aws/pull/1945).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_managed_policy (https://github.com/ansible-collections/community.aws/pull/1954).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_mfa_device_info (https://github.com/ansible-collections/community.aws/pull/1953).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_password_policy.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_role (https://github.com/ansible-collections/community.aws/pull/1948).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_role_info (https://github.com/ansible-collections/community.aws/pull/1948).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.s3_bucket_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.sts_assume_role.default_branch support for project update. If you used the module so far with default_branch to update a project, the value of default_branch was ignored. Make sure that you either do not pass a value if you are not sure whether it is the one you want to have to avoid unexpected breaking changes (https://github.com/ansible-collections/community.general/pull/7158).VarDict will no longer accept variables named _var, get_meta, and as_dict (https://github.com/ansible-collections/community.general/pull/6647).hvac is now 1.2.1 (https://docs.ansible.com/ansible/devel/collections/community/hashi_vault/docsite/user_guide.html#hvac-version-specifics).vmnics and lag_uplinks (https://github.com/ansible-collections/community.vmware/issues/1516).acceptance_level and used its options in state. This also means there will be no state list anymore. In order to get information about the current acceptance level, use the new module vmware_host_acceptance_info (https://github.com/ansible-collections/community.vmware/issues/1872).image_id, image_os_flavor and image_name) when the server image is not defined.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.aws_region_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.aws_s3_bucket_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_access_key.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_access_key_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_group (https://github.com/ansible-collections/amazon.aws/pull/1755).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_managed_policy (https://github.com/ansible-collections/amazon.aws/pull/1762).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_mfa_device_info (https://github.com/ansible-collections/amazon.aws/pull/1761).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_password_policy.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_role (https://github.com/ansible-collections/amazon.aws/pull/1760).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.iam_role_info (https://github.com/ansible-collections/amazon.aws/pull/1760).community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.s3_bucket_info.community.aws collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use amazon.aws.sts_assume_role.ansible-core 2.12 and ansible-core 2.13. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing those versions. Both are or will soon be End of Life and if you are still using them, you should consider upgrading to the latest Ansible / ansible-core 2.15 or later as soon as possible (https://github.com/ansible-collections/community.mysql/pull/574).column_case_sensitive argument’s default value will be changed to true in community.mysql 4.0.0. If your playbook expected the column to be automatically uppercased for your roles privileges, you should set this to false explicitly (https://github.com/ansible-collections/community.mysql/issues/578).column_case_sensitive argument’s default value will be changed to true in community.mysql 4.0.0. If your playbook expected the column to be automatically uppercased for your users privileges, you should set this to false explicitly (https://github.com/ansible-collections/community.mysql/issues/577).order argument. The sortorder sdu is hardcoded (https://github.com/ansible-collections/community.postgresql/pull/496).usage_on_types argument. Use the type option of the type argument to explicitly manipulate privileges on PG types (https://github.com/ansible-collections/community.postgresql/issues/208).path_to_script and as_single_query arguments. Use the postgresql_script module to run queries from scripts (https://github.com/ansible-collections/community.postgresql/issues/189).privs argument removal to community.postgresql 4.0.0 (https://github.com/ansible-collections/community.postgresql/issues/493).groups argument. Use the postgresql_membership module instead (https://github.com/ansible-collections/community.postgresql/issues/300).no_log feature in some modules;seq_num in fortios_router_static;member_path in all the modules;cisco.nso collection was considered unmaintained and has been removed from Ansible 9 (https://github.com/ansible-community/community-topics/issues/155). Users can still install this collection with ansible-galaxy collection install cisco.nso.community.fortios collection was considered unmaintained and has been removed from Ansible 9 (https://github.com/ansible-community/community-topics/issues/162). Users can still install this collection with ansible-galaxy collection install community.fortios.community.google collection was considered unmaintained and has been removed from Ansible 9 (https://github.com/ansible-community/community-topics/issues/160). Users can still install this collection with ansible-galaxy collection install community.google.community.skydive collection was considered unmaintained and has been removed from Ansible 9 (https://github.com/ansible-community/community-topics/issues/171). Users can still install this collection with ansible-galaxy collection install community.skydive.ngine_io.vultr collection was considered unmaintained and has been removed from Ansible 9 (https://github.com/ansible-community/community-topics/issues/257). Users can still install this collection with ansible-galaxy collection install ngine_io.vultr.ansible-galaxy collection install servicenow.servicenow._remote_checksum methodcache_block_tasks and get_original_task methodsFileLock classinclude which has been deprecated in Ansible 2.12. Use include_tasks or import_tasks instead.Templar - remove deprecated shared_loader_obj parameter of __init__
fetch_url - remove auto disabling decompress when gzip is not availableget_action_args_with_defaults - remove deprecated redirected_names method parameterdefault.fact_caching_prefix ini configuration option, use defaults.fact_caching_prefix instead.get_md5 parameter.passwordd, use url_password instead.user and username, use url_username instead.ensure, use state instead.productid, use product_id instead.username, user_name, password, and user_password. Use become with become_flags: logon_type=new_credentials logon_flags=netcredentials_only on the task instead to replicate the same functionality instead.ignore_errors: true will be treated like ignore_unreachable: true. Going forward ignore_errors: true will only ignore errors the plugin encountered and not an unreachable host. Use ignore_unreachable: true to ignore that error like any other module.path with forward slashes as a key separator. Using a forward slash has been deprecated since Ansible 2.9. If using forward slashes in the win_regedit path value, make sure to change the forward slash / to a backslash \. If enclosed in double quotes the backslash will have to be doubled up.blacklist, use reject_list instead.whitelist, use accept_list instead.use_scheduled_task. This option did not change any functionality in the module and can be safely removed from the task entry.password, use url_password instead.user and username, use url_username instead.state=absent, the options script, ttl, tcp, http, and interval can no longer be specified (https://github.com/ansible-collections/community.general/pull/7358).state=get has been removed. Use the module community.general.gconftool2_info instead (https://github.com/ansible-collections/community.general/pull/7358).access_level option. To restore the previous behavior, explicitly set it to ref_protected (https://github.com/ansible-collections/community.general/pull/7358).state=list has been removed. Use the module community.general.manageiq_policies_info instead (https://github.com/ansible-collections/community.general/pull/7358).state=list has been removed. Use the module community.general.manageiq_tags_info instead (https://github.com/ansible-collections/community.general/pull/7358).ArgFormat class has been removed (https://github.com/ansible-collections/community.general/pull/7358).CmdMixin mixin has been removed. Use community.general.plugins.module_utils.cmd_runner.CmdRunner instead (https://github.com/ansible-collections/community.general/pull/7358).CmdModuleHelper and CmdStateModuleHelper classes have been removed. Use community.general.plugins.module_utils.cmd_runner.CmdRunner instead (https://github.com/ansible-collections/community.general/pull/7358).disable_facts option was removed (https://github.com/ansible-collections/community.general/pull/7358).ansible-core is now 2.14, support for 2.13 has been dropped (https://github.com/ansible-collections/community.hashi_vault/pull/403).version (https://github.com/ansible-collections/community.vmware/issues/1639).absent and present (https://github.com/ansible-collections/community.vmware/issues/1517).get_tag_by_category() (https://github.com/ansible-collections/community.vmware/issues/1898).app_parameters, use arguments instead.url, use community.windows.win_psrepository to manage repositories insteadrepository specified when state: absent, use community.windows.win_psrepository to manage repositories insteadrepetition to be defined as a list of dictionary entries. Specify the repetition as a dictionary value rather than a list of dictionaries.dellemc_get_firmware_inventory module is removed and replaced with the module idrac_firmware_info.dellemc_get_system_inventory module is removed and replaced with the module idrac_system_info.community.azure collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See Collections Removal Process for unmaintained collections for more details, including for how this can be cancelled (https://github.com/ansible-community/community-topics/issues/263).hpe.nimble collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See Collections Removal Process for unmaintained collections for more details, including for how this can be cancelled (https://github.com/ansible-community/community-topics/issues/254).netapp.azure collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See Collections Removal Process for unmaintained collections for more details, including for how this can be cancelled (https://github.com/ansible-community/community-topics/issues/234).netapp.elementsw collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See Collections Removal Process for unmaintained collections for more details, including for how this can be cancelled (https://github.com/ansible-community/community-topics/issues/235).netapp.um_info collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See Collections Removal Process for unmaintained collections for more details, including for how this can be cancelled (https://github.com/ansible-community/community-topics/issues/244).community.sap was renamed to community.sap_libs. For now both collections are included in Ansible. The collection will be completely removed from Ansible 10. Please update your FQCNs from community.sap to community.sap_libs.ibm.spectrum_virtualize was renamed to ibm.storage_virtualize. For now both collections are included in Ansible. The content in ibm.spectrum_virtualize will be replaced by deprecated redirects in Ansible 10.0.0. The collection will be completely removed from Ansible 12. Please update your FQCNs from ibm.spectrum_virtualize to ibm.storage_virtualize.t_systems_mms.icinga_director was renamed to telekom_mms.icinga_director. For now both collections are included in Ansible. The content in t_systems_mms.icinga_director has been replaced by deprecated redirects in Ansible 9.0.0. The collection will be completely removed from Ansible 11. Please update your FQCNs from t_systems_mms.icinga_director to telekom_mms.icinga_director.collections_paths, use the singular form collections_path insteadANSIBLE_COLLECTIONS_PATHS, use the singular form ANSIBLE_COLLECTIONS_PATH insteadget_host_vars or get_group_vars are deprecated. The plugin should be updated to inherit from BaseVarsPlugin and define a get_vars method as the entrypoint.STRING_CONVERSION_ACTION config option is deprecated as it is no longer used in the Ansible Core code base.vaultid parameter is deprecated and will be removed in ansible-core 2.20. Use vault_id instead.tenancy and placement_group in favor of placement attribute (https://github.com/ansible-collections/amazon.aws/pull/1825)./ has been deprecated and will be removed in a release after 2025-12-01 (https://github.com/ansible-collections/amazon.aws/pull/1549).setup module. These OS’ are nearing the End of Life and will not be tested in CI when that time is reached.microsoft.ad.domain module, the ansible.windows.win_domain module will be removed in the 3.0.0 release of this collection.microsoft.ad.domain_controller module, the ansible.windows.win_domain_controller module will be removed in the 3.0.0 release of this collection.microsoft.ad.membership module, the ansible.windows.win_domain_membership module will be removed in the 3.0.0 release of this collection.false of the asn1_base64 option is deprecated and will change to true in community.crypto 3.0.0 (https://github.com/ansible-collections/community.crypto/pull/600).cmd_runner_fmt.as_default_type() formatter (https://github.com/ansible-collections/community.general/pull/6601).VarsMixin and supporting classes in favor of plain vardict module util (https://github.com/ansible-collections/community.general/pull/6649).ack_ansible29 and ack_min_ansiblecore211 options have been deprecated and will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/7358).ack_params_state_absent option has been deprecated and will be removed in community.general 10.0.0 (https://github.com/ansible-collections/community.general/pull/7358).compatibility is deprecated as default for parameter mode (https://github.com/ansible-collections/community.general/pull/6512).logging in favour of producing more detailed information in the module output (https://github.com/ansible-collections/community.general/pull/7043).proxmox_default_behavior will be removed in community.general 10.0.0 (https://github.com/ansible-collections/community.general/pull/6836).proxmox_default_behavior (https://github.com/ansible-collections/community.general/pull/7377).10 for the timeout option is deprecated and will change to 60 in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/7295).module_utils.redhat module is deprecated, as effectively unused: the Rhsm, RhsmPool, and RhsmPools classes will be removed in community.general 9.0.0; the RegistrationBase class will be removed in community.general 10.0.0 together with the rhn_register module, as it is the only user of this class; this means that the whole module_utils.redhat module will be dropped in community.general 10.0.0, so importing it without even using anything of it will fail (https://github.com/ansible-collections/community.general/pull/6663).autosubscribe alias for the auto_attach option has been deprecated for many years, although only in the documentation. Officially mark this alias as deprecated, and it will be removed in community.general 9.0.0 (https://github.com/ansible-collections/community.general/pull/6646).pool option is deprecated in favour of the more precise and flexible pool_ids option (https://github.com/ansible-collections/community.general/pull/6650).state=present has not been working as expected for many years, and it seems it was not noticed so far; also, “presence” is not really a valid concept for subscription repositories, which can only be enabled or disabled. Hence, mark the present and absent values of the state option as deprecated, slating them for removal in community.general 10.0.0 (https://github.com/ansible-collections/community.general/pull/6673).community.postgresql 4.0.0. Please use the postgresql_ext module instead (https://github.com/ansible-collections/community.postgresql/issues/559).microsoft.ad.computer module, the community.windows.win_domain_computer module will be removed in the 3.0.0 release of this collection.microsoft.ad.group module, the community.windows.win_domain_group module will be removed in the 3.0.0 release of this collection.microsoft.ad.group module, the community.windows.win_domain_group_membership module will be removed in the 3.0.0 release of this collection.microsoft.ad.object_info module, the community.windows.win_domain_object_info module will be removed in the 3.0.0 release of this collection.microsoft.ad.ou module, the community.windows.win_domain_ou module will be removed in the 3.0.0 release of this collection.microsoft.ad.user module, the community.windows.win_domain_user module will be removed in the 3.0.0 release of this collection.junos_ospfv2 - add deprecate warning for area_range.nqn, wwns, host_password, host_user, target_password`and `target_user were deprecatedendpoint_type parameter is now deprecated and will be removed in version 2.0.0
© 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_9.html