mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-08-22 05:51:43 -07:00
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>
This commit is contained in:
parent
66cb9aefb5
commit
1956815884
2 changed files with 3 additions and 0 deletions
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue