-
Notifications
You must be signed in to change notification settings - Fork 24k
Add notes for DNF module about caveats when ensuring presence of groups #81452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: devel
Are you sure you want to change the base?
Conversation
The test
The test
The test
|
the underlying DNF API may upgrade packages within the group to ensure they | ||
align with the group's current metadata definitions. If you aim to merely | ||
check for the presence of a group without potentially upgrading its | ||
packages, additional considerations, or checks might be necessary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would point at package_facts or check_mode for this use case, as 'present' and check_mode: no is expected to modify a system to match the stated group presence.
@codyro Are you still working on this? Thanks. |
I thought this got picked up by someone else. Added to my agenda. |
SUMMARY
Add additional notes to the
dnf
module/documentation about the behavior of thednf
API's handling of groups.ISSUE TYPE
ADDITIONAL INFORMATION
When using
state: present
in conjunction with a package group (EX:@Core
), it is possible that a package in the group can be updated regardless of thestate: present
, causing breaking or unexpected results.test-dnf-module.yml