Hi,
it should read ${values.kernel}.
Cheers,
Thomas
Am 22.03.2017 um 11:56 schrieb Rudy Gevaert:
Hi,
I'm very impressed with the director approach. I hope it can live up to
be usable for automation and still for end users. Like it promises.
What I have tested I really nice!
II got the CSV import working with fileshipper. I want to try to import
my Puppet facts (for now with the fileshipper, I'll also try PuppetDB
shipper)
I was able to import the directory on the filesystem with Director.
I'm configuring the sync rule, but I'm stuck.
The yaml files has this data:
--- !ruby/object:Puppet::Node::Facts
name: gamba1.ugent.be
values:
filesystems: "btrfs,ext3"
boardproductname: "440BX Desktop Reference Platform"
boardserialnumber: None
kernel: Linux
ipaddress: 1.1.1.1
...
I'm having trouble setting up the sync. Unfortunately I need to go two
levels deep.
How can I access value '1.1.1.1' above?
$values[ipaddress]
$values{ipaddress]
All get translated to "$values{ipaddress]"
E.g.
object Host "myhost.be" {
address = "$values[ipaddress]"
}
A second question. Then import setting isn't in the source file, I can
add it manually (I did that for my csv import) as a static translation
(defined in the properties)
But do I need to really do it for every import?
Thank you in advance,
Rudy
--
Thomas Gelf
Principal Consultant
NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | thomas.g...@netways.de
** OSDC 2017 - Mai - osdc.de **
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
