Skip to content

Commit

Permalink
rename whitelist to allowlist
Browse files Browse the repository at this point in the history
  • Loading branch information
xorpaul committed May 25, 2022
1 parent 4df80ea commit 97696e0
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -413,20 +413,20 @@ sources:

- Added support for r10k-like purge behaviour of stale content

Starting with [v.0.7.0](https://github.com/xorpaul/g10k/releases/tag/v0.7.0) g10k supports the r10k-like purge behaviour of stale content with the different configuration settings `purge_level` and `purge_whitelist` as documented [here for purge_levels](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd#purge_levels) and [here for purge_whiltelist](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd#purge_whitelist)
Starting with [v.0.9.0](https://github.com/xorpaul/g10k/releases/tag/v0.9.0) g10k supports the r10k-like purge behaviour of stale content with the different configuration settings `purge_level` and `purge_allowlist` as documented [here for purge_levels](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd#purge_levels) and [here for purge_allowlist](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd#purge_allowlist)

Please check if you need to whitelist files/folders inside your Puppet environments!
Please check if you need to allowlist files/folders inside your Puppet environments!

As an additional setting, you can also whitelist Puppet environments with `deployment_purge_whitelist`, that would've been purged by the [deployment](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd#deployment) `purge_level`.
As an additional setting, you can also allowlist Puppet environments with `deployment_purge_allowlist`, that would've been purged by the [deployment](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd#deployment) `purge_level`.
This can be helpful if you have a similar source name or prefix set. E.g. having a source called `foobar` and another one `foobar_hiera` would have purged all foobar_hiera_\* branches if there are not branches called `hiera_master` or similar in the `foobar` source.

Example:
```
---
deploy:
purge_levels: ['deployment', 'puppetfile', 'environment']
purge_whitelist: [ '.latest_revision', '.resource_types', 'resource_types/*.pp', '**/*.pp'. ]
deployment_purge_whitelist: [ 'example_hiera_*', '.resource_types' ]
purge_allowlist: [ '.latest_revision', '.resource_types', 'resource_types/*.pp', '**/*.pp'. ]
deployment_purge_allowlist: [ 'example_hiera_*', '.resource_types' ]
sources:
example:
Expand Down

0 comments on commit 97696e0

Please sign in to comment.