Skip to content

Commit

Permalink
functions: Fix formatting for package*matching
Browse files Browse the repository at this point in the history
  • Loading branch information
btriller committed Jan 31, 2025
1 parent ab1bc57 commit b4e8c77
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 4 deletions.
5 changes: 3 additions & 2 deletions reference/functions/packagesmatching.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -46,10 +46,12 @@ some desired packages, and finally reports if they are installed.
[%CFEngine_include_example(packagesmatching.cf)%]

**Refresh rules:**

* installed packages cache used by packagesmatching() is refreshed at the end of each agent run in accordance with constraints defined in the relevant package module body.
* installed packages cache is refreshed after installing or removing a package.
* installed packages cache is refreshed if no local cache exists.
This means a reliable way to force a refresh of CFEngine's internal package cache is to simply delete the local cache:

This means a reliable way to force a refresh of CFEngine's internal package cache is to simply delete the local cache:

```cf3
$(sys.statedir)/packages_installed_<package_module>.lmdb*
Expand All @@ -65,7 +67,6 @@ $(sys.statedir)/software_packages.csv
**History:**

* Introduced in CFEngine 3.6

* Function started using `package_module` based data sources by default, even if
there is no `package_inventory` attribute defined in `body common control` if
available in 3.23.0
Expand Down
5 changes: 3 additions & 2 deletions reference/functions/packageupdatesmatching.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -50,10 +50,12 @@ vars:
```

**Refresh rules:**

* updates cache used by packageupdatesmatching() is refreshed at the end of each agent run in accordance with constraints defined in the relevant package module body.
* updates cache is refreshed every time `repo` type package is installed or removed
* updates cache is refreshed if no local cache exists.
This means a reliable way to force a refresh of CFEngine's internal package cache is to simply delete the local cache:

This means a reliable way to force a refresh of CFEngine's internal package cache is to simply delete the local cache:

```cf3
$(sys.statedir)/packages_updates_<package_module>.lmdb*
Expand All @@ -68,7 +70,6 @@ $(sys.statedir)/software_patches_avail.csv
**History:**

* Introduced in CFEngine 3.6

* Function started using `package_module` based data sources by default, even if
there is no `package_inventory` attribute defined in `body common control` if
available in 3.23.0
Expand Down

0 comments on commit b4e8c77

Please sign in to comment.