On 06/10/17 09:11, Michael Watters wrote:
You do not *have* to quote strings however I have ran into issues with hiera
turning strings that look like integers into an integer which causes problems
when you attempt to do a key lookup using a string value or pass a value to a
parameter that expe
On 06/10/17 11:28, Daniel Urist wrote:
I've noticed in classes with multiple templates that ERB variables seem
to share a single scope. That caught me by surprise-- is that intended
behavior?
Intended or not - that is the behavior, and this is Ruby so it is
possible to mutate things that sh
I've noticed in classes with multiple templates that ERB variables seem to
share a single scope. That caught me by surprise-- is that intended
behavior?
Here's a simple test case:
class erb_scope_test (
)
{
$myarr1 = [ 'one' ]
$myarr2 = [ 'two' ]
$str1 = inline_template("<%= @myarr1.concat
I encountered this very same problem installing puppetDB v4.4 from RPM on
CentOS 7.2.1511, with postgres v9.4 installed via RPMs retrieved from
yum.postgresql.org.
I tried following the instructions here for creating the puppetdb role and
database in postgresql:
https://docs.puppet.com/puppetdb
You do not *have* to quote strings however I have ran into issues with hiera
turning strings that look like integers into an integer which causes problems
when you attempt to do a key lookup using a string value or pass a value to a
parameter that expects a string value.
For example, there is
Hi,
The database connections leak remains after upgrading trocla.
Also after 2 days the catalog computation times start to increase again.
I'm going to install newrelic on a puppetserver and if I see nothing I will try
to analyze via your blog article.
Best regardsLe 4 oct. 2017 10:58, Poil a
Hi
how to use the option "server_list" which is available in puppet 4.6?
https://docs.puppet.com/puppet/4.6/release_notes.html#specify-multiple-masters-with-serverlist-option
I tried with two different puppet server instances and i am facing
certificate issues when the active/first server fails.
Apologies, I didn't spot the extra quotes (or read properly what you said
about them) I clearly need more coffee... Yes, that does work...
---
"foo.bar.tango": bar
$bar = lookup("'foo.bar.tango'")
notify { $bar: }
Notice: /Stage[main]/Main/Notify[bar]/message: defined 'message' as 'bar'
On Thu, Oct 5, 2017 at 6:44 PM, Henrik Lindberg
wrote:
> On 04/10/17 08:54, John Baird wrote:
>
>>
>> Something like "lookup('/path/to/somefile.txt', scope=false)"... In this
>> manner, the user and more specifically, each lookup call can determine
>> whether or not to include the dotted key.
>>
