@John Ratliff historically in puppet facts were just top scope variables, later they were all made available under the $facts variable. There is a desire to stop facts from being top scope variables - there are several reasons; i) it takes more processing power to create all the individual variables as opposed to the single $facts ii) the names of custom facts can clash with other top scope things iii) it is bad idea in general to have lots of top scope variables. The big problem with getting rid of them altogether is that the most frequent facts would require more keystrokes, and those are pretty much used everywhere.

Further, IIRC, the mapped path construct can only be used with actual facts and not top scope variables in general. The feature was introduced as it would otherwise be impossible to cut in between facts and any transformation of facts for use in interpolation into hierarchy paths.

Specifically to be able to have a list of paths based on a fact holding an array.

At least as of Puppet 6, you can at least use node-scope variables with

mapped_paths

. Not sure when that was added but we're using it successfully

I'm not sure about global scope, though

It definitely worked with my custom fact.

Big caveat is that functions don't have access to node-scope variables, which will cause

mapped_paths

not to work as expected unless you pass in the node-scope variable to the function.

ok, maybe it changed, or I remembered it wrong

@John Ratliff well, your custom fact would work in any case since it is a fact 🙂

It is worth mentioning that when making stuff in hiera.yaml depend on the values of variables (as opposed to facts), you will always need to use the hiera command line tool with the compilation option. You want to avoid this as much as possible - but understandable if it needs to be done since it is not possible to call functions directly from hiera.yaml (other than using the built in

mapped_paths

). Still, you want to avoid doing this even if it works.

message has been deleted

apache::vhost { "$xyz03": ensure => 'present', port => 80, docroot => '/var/www', serveradmin => $admin_localhost, servername => $xyz03, notify => [ Service['apache2'], ], directories => [ { path => '/api', auth_name => 'LDAP Auth for API', auth_type => 'Basic', auth_basic_provider => 'ldap', auth_ldap_url => 'ldap://ldap-xyz.software.com/dc=XYZ-DOMAIN?sAMAccountName', require => 'ldap-group CN=V1_DEP_ITServ-AppMgmt,OU=Departments,OU=Groups,OU=Benutzer,DC=XYZ-DOMAIN', }, proxy_pass => [{ 'path' => '/apis/1/', 'url' => 'http://localhost:8091/', }, { 'path' => '/apis/2/', 'url' => 'http://localhost:8092/', }, ], ], } I don't get the proxy pass details(1 and 2) when i run puppet agent but i can see the other details.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Those 3 specific values? Or the pattern "app-<4 digits>"?

will it always be 3 of them? or can it be a single one or multiple occurrences, each separated by the pipe?

It can be single one or multiple occurrence

$ puppet lookup -E jdratlif --node <http://test-node.example.com|test-node.example.com> --explain test_fact
Error: Could not run: Lookup of key 'lookup_options' failed: Lookup using eyaml lookup_key function is only supported when the hiera_eyaml library is present

Why would I see this error on my puppet server when using

puppet lookup

. We are using eyaml, and our puppet runs fine, but I cannot use puppet lookup from CLI here.

$ puppet lookup -E jdratlif --node <http://test-node.example.com|test-node.example.com> --explain test_fact
Error: Could not run: Lookup of key 'lookup_options' failed: Lookup using eyaml lookup_key function is only supported when the hiera_eyaml library is present

Why would I see this error on my puppet server when using

puppet lookup

. We are using eyaml, and our puppet runs fine, but I cannot use puppet lookup from CLI here.

CentOS7 and puppet 4.10.12

You'll need to install the hiera-eyaml gem into the puppet agent Ruby stack.

This message was deleted.

You'll need to install the hiera-eyaml gem into the puppet agent Ruby stack.

This message was deleted.

Hi community, the vscode plugin didnt see a release in about a year. But there are valuable changes. Is there a chance to cut a new release? https://github.com/puppetlabs/puppet-vscode/compare/1.4.0...main

message has been deleted