It is currently counter-intuitive that something like:
# File '/thing' contents
#SomeSetting WrongValue
# Manifest
__line '/thing' \
--line 'SomeSeting GoodValue' \
--regex '^(#[[:space:]]*)?SomeSetting[[:space:]]'
Produces:
# Resulting '/thing' contents
#SomeSetting WrongValue
This makes sense given the implementation, but it masks a very common use-case.
Changing the default behaviour for such a base type is not really an option, so
instead we add a `replace` as a valid value for `--state`, which would result
in:
# Resulting '/thing' contents with: --state replace
SomeSetting GoodValue
For compatibility, if the regex is missing, `--state replace` behaves just as
`--state present`.
|
||
|---|---|---|
| .. | ||
| explorer | ||
| manifest | ||
| type | ||
| .gitignore | ||
| README | ||
This is a sample configuration that can be used as an example for /etc/cdist. For instance: [root@kr etc]# ln -s ~nico/p/cdist/conf/ /etc/cdist