Skip to content
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

Clarify functionality of CLM package/patch allow filters #3667

Merged
merged 2 commits into from
Feb 5, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
- Clarify functionality of CLM package/patch allow filters
(bsc#1236234)
- Corrected the instruction for logging in to Azure instance in
Specialized Guides (bsc#1234442)
- Updated Backup and Restore chapter regarding containerization in
Expand Down
2 changes: 1 addition & 1 deletion modules/administration/pages/content-lifecycle.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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. This means with a package filter you cannot add packages back in that were filtered out through patch filters or vice versa for patches that where filtered out through package filters.

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.

Expand Down