From 1956815884d3b14f552f5e0f9351e91ea780ec0d Mon Sep 17 00:00:00 2001 From: Felix Fontein Date: Sun, 15 Jun 2025 11:24:30 +0200 Subject: [PATCH] docs: add notes that dnf_* modules do not work with dnf5 (#10238) * Add notes that dnf_* modules do not work with dnf5. * Apply suggestions from code review. Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com> --------- Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com> --- plugins/modules/dnf_config_manager.py | 2 ++ plugins/modules/dnf_versionlock.py | 1 + 2 files changed, 3 insertions(+) diff --git a/plugins/modules/dnf_config_manager.py b/plugins/modules/dnf_config_manager.py index 2d896f3742..69ac2c7085 100644 --- a/plugins/modules/dnf_config_manager.py +++ b/plugins/modules/dnf_config_manager.py @@ -39,6 +39,8 @@ options: required: false type: str choices: [enabled, disabled] +notes: + - Does not work with C(dnf5). seealso: - module: ansible.builtin.dnf - module: ansible.builtin.yum_repository diff --git a/plugins/modules/dnf_versionlock.py b/plugins/modules/dnf_versionlock.py index eec7f3013a..d3eaf832a5 100644 --- a/plugins/modules/dnf_versionlock.py +++ b/plugins/modules/dnf_versionlock.py @@ -60,6 +60,7 @@ notes: - In an ideal world, the C(versionlock) plugin would have a dry-run option to know for sure what is going to happen. So far we have to work with a best guess as close as possible to the behaviour inferred from its code. - For most of cases where you want to lock and unlock specific versions of a package, this works fairly well. + - Does not work with C(dnf5). requirements: - dnf - dnf-plugin-versionlock