Clarify functionality of CLM package/patch allow filters (bsc#1236234)

Signed-off-by: Pascal Arlt <[email protected]>
uyuni-project · Feb 3, 2025 · a392f0f · a392f0f
1 parent af58b17
commit a392f0f
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,5 @@
+- Clarify functionality of CLM package/patch allow filters
+  (bsc#1236234)
 - Corrected the wording in the procedure in Administration Guide
   (bsc#1236625)
 - Improved documentation on CLM filters in Administration Guide

diff --git a/modules/administration/pages/content-lifecycle.adoc b/modules/administration/pages/content-lifecycle.adoc
@@ -107,7 +107,7 @@ Each filter has a ``rule`` parameter that can be set to either ``Allow`` or ``De
 The filters are processed like this:
 
 * If a package or patch satisfies a ``Deny`` filter, it is excluded from the result.
-* If a package or patch satisfies an ``Allow`` filter, it is included in the result (even if it was excluded by a ``Deny`` filter).
+* If a package or patch satisfies an ``Allow`` filter, it is included in the result (even if it was excluded by a ``Deny`` filter). ``Allow`` filters for packages only operate on package filters and ``Allow`` filters for patches only operate on patch filters, i.e. a package filter can't be used to add packages from patches that where filtered out back in and vise versa.
 
 This behavior is useful when you want to exclude large number of packages or patches using a general ``Deny`` filter and "cherry-pick" specific packages or patches with specific ``Allow`` filters.