Hello Everyone!
Today we’re happy to announce the release of Bolt 0.21.7. In this release
you will find:
- improved logging for the run_plan function
- fix to validation for RBAC token files with white space
For more information, see:
https://puppet.com/docs/bolt/0.x/bolt_release_notes.h
> Is there in fact any reason for concern that applying class autofs before
applying one or both of the other two might result in a Puppet failure or a
target system misconfiguration?
In this case, yes. In order for autofs to work properly NFS must be
configured first and in order for NFS to
Henrik Lindberg wrote:
> You cannot give arguments to lookup as an interpolation function
> inside of data. Use the commented out variant. Then use
> lookup_options (in your data) to configure that lookup of 'variables'
> should always be a 'deep' merge.
Great, works now, thanks a lot!
--
You r
On 2018-08-16 15:51, Helmut Schneider wrote:
Henrik Lindberg wrote:
If your data looks like this:
variables:
baculaWorkingDirectory: '/var/lib/bacula'
Then you do not have a variables.debug key - you can lookup
variables, or variables.baculaWorkingDirectory
common.yaml:
---
netconfig
Henrik Lindberg wrote:
> If your data looks like this:
>
> >> variables:
> >>baculaWorkingDirectory: '/var/lib/bacula'
>
> Then you do not have a variables.debug key - you can lookup
> variables, or variables.baculaWorkingDirectory
common.yaml:
---
netconfig:
variables:
debug:
On 2018-08-16 14:47, Helmut Schneider wrote:
Helmut Schneider wrote:
common.yaml:
variable:
baculaWorkingDirectory: '/var/lib/bacula'
variables:
baculaWorkingDirectory: '/var/lib/bacula'
config.pp:
[...]
$variables = lookup({
"name" => "variables",
"merge" => {
"stra
Helmut Schneider wrote:
> common.yaml:
> variable:
> baculaWorkingDirectory: '/var/lib/bacula'
>
> variables:
> baculaWorkingDirectory: '/var/lib/bacula'
>
> config.pp:
> [...]
> $variables = lookup({
> "name" => "variables",
> "merge" => {
> "strategy" => "deep",
> "kn
