A bit late to the party here, but in my (rspec-puppet) tests I have created
a mock version of the function in a before(:each) block in the unit test
for the class, like this:
before(:each) do
Puppet::Parser::Functions.newfunction(:query_nodes, :type => :rvalue) {
|_| ["foo.example.com", "bar
Overall I think this looks pretty good, but I have some questions and
comments.
For implementations that can't enumerate all existing resources (at least
not in any fast way), like for example File, should they fine a get method
that returns an empty hash, nil or just not define a get method? nil
I've just released version 2.0 of the puppetdbquery module. It uses the new
v4 API in PuppetDB, so version 3.x of PuppetDB is required.
The highlights are:
- v4 API support
- support for structured facts, example: system_uptime.days>209
- arbitrary subqueries using # sign, example:
#node.catalo
Yeah, I'm not really using puppet server (yet at least) or the postgres
hiera backend. So if someone else wants to take over maintainership of it I
can transfer the repo ownership.
On Tue, 19 May 2015 at 18:51 Tony Thayer wrote:
> Actually, I just realized I was using my own fork of the original
We are running a PuppetDB instance with ~8000 clients using a 30 minute
runinterval. We have hit some scaling issues in the past but the latest
PuppetDB version (2.3.5) is running nicely for us. This is with
stringify_facts=false, which does create some extra load compared with
stringify_facts=true
Note that you can also just put the standard classes (and variables)
directly in the top scope. No real need to encapsulate them inside a node
scope (unless you are overriding the value of facts in the manifest, but
that seems like a pretty bad idea anyway).
A minor difference is also that resourc
On Mon Dec 15 2014 at 6:07:43 PM John Sellens wrote:
> I couldn't find any reference to this different behaviour, so I'm
> wondering if anyone knows if this is intentional.
>
> I use a bunch of defined types, and with the future parser, when I refer
> to a variable in a template, it seems that th
On Fri Dec 12 2014 at 7:06:20 PM Henrik Lindberg <
henrik.lindb...@cloudsmith.com> wrote:
> On 2014-12-12 2:59, Erik Dalén wrote:
> > Just wanted to say that we have now switched completely to the future
> > parser at Spotify, and it is working well. Still have some w
:)
These were really easy to find using git grep though.
> Thanks!
>
> Trevor
>
> On Fri, Dec 12, 2014 at 2:59 AM, Erik Dalén
> wrote:
>
>> Just wanted to say that we have now switched completely to the future
>> parser at Spotify, and it is working well. Stil
Just wanted to say that we have now switched completely to the future
parser at Spotify, and it is working well. Still have some work to do to
take advantage of all the new stuff, it is still mostly the old manifests
running on the new parser.
We had some syntax fixes we had to make to get it work
rvers though.
On Thu Oct 30 2014 at 10:39:00 PM Walid wrote:
> Hi Erik,
>
> What was the largest practical number of nodes tested against it, or
> configured.
>
> Best regards,
>
> Walid
>
> On 26 August 2014 16:04, Erik Dalén wrote:
>
>> A new release of Pu
We do this, but could probably live without it. But we do it using the
facts indirector and setting it up to cache to puppetdb.
On 27 Sep 2014 15:28, "Ken Barber" wrote:
> > Hmm... I didn't even know this existed. Ironically, given your question,
> it
> > sounds like something I'd want to use. Bu
gt;
>> Out of curiosity, how does it compare with puppet dashboard ?
>>
>> Is Puppet Dashboard really EOL ?
>>
>> What's currently the best reporting open source solution for Puppet ?
>>
>> Cheers
>>
>>
>> On Friday, September 12, 2014 5:19:2
thub.com/spotify/puppetexplorer/releases
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view
10.216.61.76 is *not* the local IP of the puppet master... its the
>> remote IP of the ELB, which indicates that its remote traffic from our
>> puppet clients.
>>
>>
>
> That traffic might be coming from nodes, but all you know for sure is that
> it is traversin
oming structured facts support in
PuppetDB 2.2+
pre build deb:
http://dl.bintray.com/dalen/puppetexplorer-apt/puppetexplorer_1.2.0-1_amd64.deb
tar.gz:
http://dl.bintray.com/dalen/puppetexplorer/puppetexplorer-1.2.0.tar.gz
--
Erik Dalén
Systems Engineer, Site Reliability Engineering
--
You received
ppet-users/e4f858b9-ecc7-4b9b-962f-f7d6554d9f0b%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/e4f858b9-ecc7-4b9b-962f-f7d6554d9f0b%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
installation can be found here:
tar.gz:
http://dl.bintray.com/dalen/puppetexplorer/puppetexplorer-1.1.0.tar.gz
deb:
http://dl.bintray.com/dalen/puppetexplorer-apt/puppetexplorer_1.1.0-1_amd64.deb
--
Erik Dalén
Systems Engineer, Site Reliability Engineering
--
You received this message because you
-apt/puppetexplorer_1.0.0-1_amd64.deb
A initial puppet module to manage it can be found here:
https://github.com/spotify/puppet-puppetexplorer
--
Erik Dalén
Systems Engineer, Site Reliability Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet
40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this grou
https://groups.google.com/d/msgid/puppet-users/dc3a5a66-8f3d-4efc-b1ab-e0f262efa746%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Erik Dalén
--
You received this message because you are subscribed to the Google G
Debian has announced a long term support for debian squeeze:
https://www.debian.org/News/2014/20140616
I'm wondering if this will mean that Squeeze will stick around at
apt.puppetlabs.com for the same period?
--
Erik Dalén
--
You received this message because you are subscribed to the G
Btsug%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this
There is also $::clientnoop that can be used as default value. But usually
you would just want it unspecified.
On 13 May 2014 14:53, "jcbollinger" wrote:
>
>
> On Monday, May 12, 2014 1:06:34 PM UTC-5, Jakov Sosic wrote:
>>
>> On 05/12/2014 03:16 PM, Christopher Wood wrote:
>> > I get the same be
That seems like a pretty bad bug. It is best if you file a issue about it
in JIRA so it doesn't get lost. jira.puppetlabs.com
On 13 Mar 2014 19:14, "Toan Ngo" wrote:
> I'm running puppet 3.4.3 with hiera 1.3.2. I've been tracking this odd
> bug with my SSH module losing it's service name and lib
ved this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https:
ubscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/
n old ruby versions
- Improve facts query output
- Support single quoted strings in queries as well as double quoted
http://forge.puppetlabs.com/dalen/puppetdbquery
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To u
e a proper benchmark though.
On 15 January 2014 09:48, Matthias Saou wrote:
> On Tue, 14 Jan 2014 16:31:40 +0100
> Erik Dalén wrote:
>
> > I did a bit of a hack to serve the static files in the Puppet CA
> > directly using Apache instead of going through the Ruby laye
https://gist.github.com/dalen/8419913
Works for me, but no guarantees etc :)
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet
roup.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/9c413f3f-733a-4269-a36c-f5a869db008f%40googlegroups.com
>
t; "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/9f5a8416-960f-470d-84b8-1903c0315f00%40googlegrou
ups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an ema
>> email to puppet-users...@googlegroups.com.
>>
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/puppet-users/18ad2d51-9259-4abb-97a4-5b28bd77eee0%
>> 40googlegroups.com.
>> For more options, visit https://groups.google.com/gr
Well, that is actually all resources managed rather than all resources
changed. The changed resources are in the report. In my case we use
puppetdb for report querying.
On 18 December 2013 17:41, Erik Dalén wrote:
> If that is all you want, run it with --write-catalog-summary and examine
&g
cts data from the catalog and report files before you can focus on the
>> analysis.
>> --
>> Charlie Sharpsteen
>> Open Source Support Engineer
>> Puppet Labs
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Pupp
gt; To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/52A762C7.8080709%40puppetlabs.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Erik Dalén
--
You received this message because you are subscribed to the Google Gr
ups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/
t: eric0
>>>
>>> puppet platform // coffee // techno // bicycles
>>>
>>>
>>> [puppetlabs-ntp]: https://github.com/apenney/**
>>> puppetlabs-ntp/tree/data-in-**modules<https://github.com/apenney/puppetlabs-ntp/tree/data-in-modules>
>>>
cr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Erik Dalén
--
You received this message because
ut before storing the report in PuppetDB.
>>
>> * Log a message when a request is blocked due to the certificate
>> whitelist:
>> prior to 1.5, when a query or command was rejected due to PuppetDB's
>> certificate
>> whitelist configuration, there was no l
scribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users.
>> For more opti
makes different assumptions about the form
> of incoming hostnames:
>
> $env = regsubst($hostname, '.*-(dev|int|ga|prod)-.*', '\1')
>
>
>
I think a custom fact for it is nice because it makes it accessible outside
of puppet if you want to. And it would also be s
s. Each puppet setup has its own CA. The puppetmasters in the
children are agents to the main puppet infrastructure, so they have a
separate ssldir for the master. With this change it just worked out of the
box if we co-hosted a puppetdb instance on them as it would use the ssldir
from the master.
--
E
/scp/rsync
them in.
https://github.com/dalen/simple-puppet-forge
Requires Sinatra and GNU tar.
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an em
received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
>
> To post to this group, send email to puppet-us
t: /etc/hosts
>>> ip: 172.16.89.81
>>> host_aliases:
>>> - xyz
>>> - bigben
>>> classes:
>>> - hosts
>>> (..)
>>>
>>>
>>> Thanks.
>>>
>>> --
>>> You received this me
; —
>
> Daniele Sluijters
>
> Nedap | Steppingstone
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+un
On 13 July 2013 15:00, Ashley Penney wrote:
> On Sat, Jul 13, 2013 at 7:15 AM, Erik Dalén
> wrote:
>
>> I've been missing a way to set which server(s) should be preferred. We
>> generally include all our NTP servers in the config but prefer the one that
>> is
ps.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Erik Dalén
--
You received this message because you are subscribe
is group, send email to puppet-users@googlegroups.com.
> Visit this group at
> http://groups.google.com/**group/puppet-users<http://groups.google.com/group/puppet-users>
> .
> For more options, visit
> https://groups.google.com/**groups/opt_out<https://groups.google.com/grou
se you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit t
You can turn it off by not having the ENC set any environment. So comment
that part out from your ENC script.
On 11 Jun 2013 16:06, "Peter Van Biesen" wrote:
> Hi,
>
> we recently upgraded from 2.7 to 3.2. We do not use ENC but use the
> node.rb for uploading the reports to foreman. However, the
and just show all
events. Will try to add that.
Also, you can't filter for events matching stuff like resource name,
property name, old value, new value etc. But hope it proves useful for you
anyway.
On 7 June 2013 21:15, Erik Dalén wrote:
> I have worked a bit on a event query tool,
googlegroups.com.
> > Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet
ering when you are going to add some support for current puppetdb
> report API ..
>
> Thanks,
> Hai
>
> On Fri, Jun 7, 2013 at 11:13 AM, Erik Dalén
> wrote:
>
>> I've released version 1.2.0 of puppetdbquery.
>>
>> New for this release is auto capital
alization on the resource title only happens if the resource type is
class, so not on stuff like 'File["/etc/passwd"]'.
It also includes a fix to make it run better under certain ruby 1.8.7
versions.
http://forge.puppetlabs.com/dalen/puppetdbquery/1.2.0
--
Erik Dalén
--
You rec
A resource declaration doesn't create a new variable scope, so the $title
variable has the value of the scope containing the resource, in this case
stage main.
On 29 May 2013 08:28, wrote:
> I have a file with this code in it:
>
> notify {'a':
> message => "${title}"
> }
>
> The output after
#x27;, 'ipaddress']
or a hash:
ntp::servers::_nodequery:
query: 'Class[Ntp::Server]'
fact: 'ipaddress'
When returning facts only nodes that actually have the fact are returned,
even if more nodes would in fact match the query itself.
--
Erik Dalén
nstalling new nodes until we have restored that part to
another node. But we have looked into some solutions for maybe making it
more resilient though.
For PuppetDB we have two service nodes and a master and hot standby for the
postgres database.
--
Erik Dalén
--
You received this mess
sier. For example you
could make a single query to get the puppet version of all nodes that failed
any resource within the last 30 mins.
Any suggestions for nifty syntax for puppetdbquery to query stuff like that? :)
--
Erik Dalén
--
You received this message because you are subscribed to the G
On 4 May 2013 13:37, Martin Langhoff wrote:
> On Sat, May 4, 2013 at 7:33 AM, Erik Dalén
> wrote:
> > I'd definitely configure the servers and
> > clients for those protocols using Puppet.
>
> Is that what you do, or what you _would_ do? ;-)
>
It is what I do
http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and s
e is EOL as well.
It is the same situation with the Ruby interpreter itself on squeeze,
upstream it is EOL but the Debian project will backport security fixes
until sqeeeze is EOL.
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users
coping for variables was.
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this
-dev+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-dev?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Erik Dalén
--
You received this
it could be that you have a ulimit for the amount of ram the puppetmaster
process (or puppet user) can use.
--
Erik Dalén
On Monday 8 April 2013 at 12:28, Mamta Garg wrote:
> Hi jcbollinger ,
>
> I have added 1 GB more RAM on server and now my free RAM is more than 2
> GB.
http://projects.puppetlabs.com/issues/15561 .
In the new 1.0.0-pre2 I've added the ability to use other kinds of HTTP
connection objects though and use a regular one in the find-nodes binary, so
you can try that instead of the puppet face if you are still getting SSL
errors.
--
Erik Dalén
On Thursda
cursive hiera lookups? (which would be really nice, especially in
backends that don't support references)
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails
nseAuthentication: "no"
> GSSAPIAuthentication: "yes"
> GSSAPICleanupCredentials: "yes"
> UsePAM: "yes"
> *ClientAliveInterval*: "100"
>
> Is this possible with my Hiera definition?
>
>
> Thank you,
> Alex
>
Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.googl
command "passenger-status" instead of
looking at the pending tasks in dashboard, that will show very different
things. Pending tasks in dashboard is not really relevant for this.
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users
query.
Anyway, please test it and send me feedback (dalen on freenode). The old
functions are left intact but deprecated, so it shouldn't affect any existing
code using the older functions.
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.
r would you
>> need something more granular than that (for instance, can query metrics but
>> not facts)?
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop rec
On Feb 8, 2013 8:35 PM, "Jo Rhett" wrote:
>
> So PL has been telling us that puppet kick is dead, and to shift to
mcollective agent. The idea of getting away from 800mb puppet agents has a
lot of appeal. Here's some advisories and bugs to watch before you make the
shift. If you are preparing to ma
Puppet dashboard doesn't use the puppetdb reports (yet at least), so to get
reports into puppet dashboard you need to use the http report handler and set
reporturl to point to your puppet dashboard server.
--
Erik Dalén
On Monday 28 January 2013 at 15:20, Tony McMahon wrote:
> Hi
On Friday, 19 October 2012 20:11:51 UTC+2, Nan Liu wrote:
>
> On Fri, Oct 19, 2012 at 11:09 AM, Joe Topjian
> >
> wrote:
> > Hi Nan,
> >
> > Like everyone else, I think this is great.
> >
> >>
> >> Run pocco against a modules directory:
> >>
> >> pocco /etc/puppet/modules/
> >
> >
>
One of the largest indexes was not needed and removed in the latest version
of puppetdb. So you might want to try out that version to reduce the index
sizes.
On Jan 22, 2013 8:41 PM, "Chuck" wrote:
> We didn't notice anything on Sunday. We have a decent number of resources
> that effect all node
system."
> #
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsub
On Jan 11, 2013 8:49 PM, "jcbollinger" wrote:
>
>
>
> On Friday, January 11, 2013 12:01:52 PM UTC-6, Erik Dalén wrote:
>>
>> At least in puppet 3 resource defaults are local to defines and classes
and doesn't get inherited to any included defines or c
I also use one environment per git branch. But I use a custom fact that
returns production/testing etc and then use that in the hiera hierarchy
instead of the puppet environment.
On Jan 9, 2013 7:43 PM, "Brad Ison" wrote:
> On Wed, Jan 9, 2013 at 3:11 AM, Luke Bigum wrote:
> >
> > :backends:
> >
At least in puppet 3 resource defaults are local to defines and classes and
doesn't get inherited to any included defines or classes. So to make
upgrading easier you shouldn't make any such assumptions in your code.
On Jan 11, 2013 6:47 PM, "Ilya Dmitrichenko"
wrote:
> Ok, I tried this with 2.7.2
As Stefan said you need to point it to your puppet master not your puppetdb
server.
On Jan 11, 2013 3:44 PM, "Luke" wrote:
> Thank you for your reply.
>
> I am confused as to why it is not working then. I have this set exactly
> like this in my settings:
>
> enable_inventory_service: true
>
>
> I
pagate my refresh event
> Debug: Buildbot::Slave::Instance[**openafs1]: The container Class[Main]
> will propagate my refresh event
> Debug: Class[Main]: The container Stage[main] will propagate my refresh
> event
>
>
> Thanks,
> Jason
>
> --
> You received this messa
This works (was added sometime during 2.6 cycle I think).
class foo ($stage = main) {
...
}
include foo
On Dec 14, 2012 9:52 PM, "Jakov Sosic" wrote:
> Hi.
>
> I am wondering why can't run stages get set inside the class?
>
> For example:
>
> class foo {
> stage main
> }
>
> Because, if I w
rs+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to p
l notify every resource
contained inside it, causing services to be restarted and refresh only execs to
be executed.
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-use
filter"
Order Allow,Deny
Allow from all
ProxyPreserveHost On
ProxyPass http://localhost:8080/
ProxyPassReverse http://localhost:8080/
# Filter this endpoint
SetOutputFilter puppetdb-strip-resource-params
# Deny access to this endpoint
Deny from a
to lookup keys.
It can also do reverse lookups, telling you what hosts has value x for key y.
That is really slow for lots of hosts though but it does some caching.
Anyway, available at https://github.com/dalen/hieralookup
patches, praise & criticism welcome :)
--
Erik Dalén
--
You
or use the join() function from puppetlabs-stdlib module.
--
Erik Dalén
On Monday 29 October 2012 at 05:08, Johan De Wit wrote:
> Hi,
>
> you can use inline_template, this way you can incorperate ruby code in
> your manifest
>
> $server_string = inline_templa
stall that
version and use the same version variable in the template.
--
Erik Dalén
On Tuesday 23 October 2012 at 12:04, Apple Wang wrote:
> Hi, all
>
> I have some questions about the execution sequence in puppet.
>
> The background:
> I want to install mysql package an
bs.com/projects/puppetdb/issues
>
> # See our development board on Trello:
> http://links.puppetlabs.com/puppetdb-trello
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To post to this group, send email
puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
--
Erik Dalén
--
You received this message because you are subsc
Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pu
in my installation any help?
>> Thanks
>> Luca
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/zZzw5IGBF0IJ.
puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to t
I've released a new version now that contains a fix for this, thanks
for the report.
On 1 September 2012 11:03, Erik Dalén wrote:
> I'll try to take a look at this during the weekend and see if I can
> create something that is compatible with both puppet 2.7 and 3.0. Can
> p
ot;Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/cnmWN3qKeJYJ.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@goog
ps
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/YqXFiwuWtxQJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubsc
1 - 100 of 122 matches
Mail list logo
