Re: [Puppet Users] Puppetdb upgrade - perfomance dashboard blank (mostly)

2020-08-20 Thread Austin Blatt 

Hi,

This is the manifestation of a bug in PuppetDB (PDB-4855 
<https://tickets.puppetlabs.com/browse/PDB-4855>). We just merged a fix 
for that bug and it'll be fixed in the next release.


On 8/20/20 1:08 PM, Dave Beedle wrote:
After updating puppetdb from v6.7.3 to 6.11.3, the puppetdb dashboard 
connects and begins to show data but stops after showing the version 
number.  The version number is correct.  All else seems to work.


In the log there is:
2020-08-20T20:04:49.049Z WARN  [o.e.j.s.HttpChannel] /pdb/dashboard/data
java.lang.ClassCastException: class java.lang.String cannot be cast to 
class java.lang.Number (java.lang.String and java.lang.Number are in 
module java.base of loader 'bootstrap')


Prior to updating puppetdb, java was also updated to 11.  The 
dashboard displayed properly.


Would anyone have any tips and addressing this issue?
--
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 
<mailto:puppet-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/44d8402e-5dad-47d4-9289-24d771140fa2n%40googlegroups.com 
<https://groups.google.com/d/msgid/puppet-users/44d8402e-5dad-47d4-9289-24d771140fa2n%40googlegroups.com?utm_medium=email_source=footer>.


--
Austin Blatt
Developer, Puppet

--
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a4b93965-e73f-d7ca-dd0c-4bc7c6893fb1%40puppet.com.

Re: [Puppet Users] PuppetDB is broken after Debian upgrade to Stretch

2020-08-20 Thread Austin Blatt 
core.clj:151)
> at compojure.core$routing.doInvoke(core.clj:148)
> at clojure.lang.RestFn.invoke(RestFn.java:460)
> at
> puppetlabs.puppetdb.pdb_routing$pdb_app$fn__50557.invoke(pdb_routing.clj:63)
> at compojure.core$if_context$fn__24487.invoke(core.clj:218)
> at
> ring.middleware.params$wrap_params$fn__35698.invoke(params.clj:64)
> at
> puppetlabs.puppetdb.middleware$wrap_with_certificate_cn$fn__37951.invoke(middleware.clj:77)
> at
> puppetlabs.puppetdb.middleware$wrap_with_default_body$fn__37956.invoke(middleware.clj:84)
> at
> puppetlabs.puppetdb.middleware$wrap_with_debug_logging$fn__37934.invoke(middleware.clj:41)
> at
> puppetlabs.i18n.core$locale_negotiator$fn__124.invoke(core.clj:357)
> at
> puppetlabs.trapperkeeper.services.webserver.jetty9_core$ring_handler$fn__44870.invoke(jetty9_core.clj:434)
> at
> puppetlabs.trapperkeeper.services.webserver.jetty9_core.proxy$org.eclipse.jetty.server.handler.AbstractHandler$ff19274a.handle(Unknown
> Source)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:205)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:219)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
> at
> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:724)
> at
> org.eclipse.jetty.server.handler.RequestLogHandler.handle(RequestLogHandler.java:56)
> at
> com.puppetlabs.trapperkeeper.services.webserver.jetty9.utils.MDCRequestLogHandler.handle(MDCRequestLogHandler.java:36)
> at
> org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:169)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> at org.eclipse.jetty.server.Server.handle(Server.java:531)
> at
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281)
> at
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102)
> at
> org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680)
> at java.lang.Thread.run(Thread.java:748)
> 
>
> I don't know where to look. Thanks for help.
>
> WBR, Eugene
>
> --
> 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 this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/bde62219-68b4-4580-9294-cfe8390ce7b5n%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/bde62219-68b4-4580-9294-cfe8390ce7b5n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Austin Blatt*
Developer, Puppet

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADVW12Pmc6naME%2BdVTkGMC083qU4RcVpTuRp%3DjYezq%2BT6GW%2BmQ%40mail.gmail.com.

Re: [Puppet Users] puppetdb query return values

2019-12-13 Thread Austin Blatt 
Hi Matt,

You should be able to do that now that we've finished PDB-2634
<https://tickets.puppetlabs.com/browse/PDB-2634>, which is available in
PuppetDB 6.7.0+.

The { } are still required, so a query could look like

resources[certname, parameters.address] {
  type = "Postgresql::Server::Pg_hba_rule"
  and parameters.address ~ ".*"
}


On Fri, Dec 13, 2019 at 9:54 AM Matt Zagrabelny  wrote:

> Greetings,
>
> I've looked through the puppetdb docs, in particular the PQL docs, to find
> out if I can extract a single parameter in the return value(s).
>
> I have as a PQL:
>
> resources[parameters] { type = "Postgresql::Server::Pg_hba_rule" and
> parameters.address ~ "."}
>
> I'd like to get the "address" parameter. So some pseudocode like:
>
> resources[parameters.address]
>
> I know I can post process the results, but is there a way to get a single
> parameter in PQL?
>
> Thanks,
>
> -m
>
> --
> 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 this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAOLfK3UZuh5jvdFjq5giQbifcM5RU6--oL-KDoLo0SuPMCu2KQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAOLfK3UZuh5jvdFjq5giQbifcM5RU6--oL-KDoLo0SuPMCu2KQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
*Austin Blatt*
Software Engineer
austin.bl...@puppet.com

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADVW12PXbtWAgqcjoq3c8op%2BB5iNg-7616u2ZkVtkFbRgh%3DL3A%40mail.gmail.com.

Re: [Puppet Users] PQL: How to filter "ensure => present"

2019-09-11 Thread Austin Blatt 

Hi Dirk,

You're hitting a bug that we've documented in PDB-3284 
. You need to add a 
space before the = after dotted fields like "parameters.ensure" (so it 
should look like parameters.ensure ="present" at the very least, but I'd 
suggest a space on both sides of the =). Let me know if you run into any 
other problems!


- Austin

On 9/11/19 7:01 AM, Dirk Heinrichs wrote:

Hi,

I'm currently struggling with a PQL query, which should return a set 
of resources depending on their "ensure" parameter. Following the 
example shown here 
, 
I tried the following:


puppet query 'resources {type="Sometype" and tag="Sometag" and 
exported=true and parameters.ensure="present"}'


which results in the following syntax error:

Error response 400 Bad Request from server: PQL parse error at line 1, 
column 88:


resources {type="St_device" and tag="TestGrid" and exported=true and 
parameters.ensure="present"}
  ^ 


Expected one of: [...]

I also tried present (w/o quoting), but that just sets the marker 
after the closing }.


Any idea what the correct syntax is here?

Thanks...

Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
*Phone*: +49 2226 15966 18
*Email*: dhein...@opentext.com 
*Website*: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu 
Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, 
Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If 
you are not the intended recipient (or have received this e-mail in 
error) please notify the sender immediately and destroy this e-mail. 
Any unauthorized copying, disclosure or distribution of the material 
in this e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese 
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den 
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie 
die unbefugte Weitergabe dieser Mail sind nicht gestattet.

--
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/44bbf09bd8128d8cf7837718cd25d4bcfdd10395.camel%40opentext.com 
.


--
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3909d9f9-9561-103c-ae25-6d03dee20565%40puppet.com.

Re: [Puppet Users] PuppetDB 5.2: How to find list of certnames from puppetdb where serverrole is "umg" using API

2019-07-16 Thread Austin Blatt 
Apologies in advance if I didn't interpret your query properly, but I
believe you are looking to return the certnames of servers that have a
specific fact with a specific value, the best endpoint for that would
probably be inventory
<https://puppet.com/docs/puppetdb/6.3/api/query/v4/inventory.html> (or
maybe fact-contents
<https://puppet.com/docs/puppetdb/6.3/api/query/v4/fact-contents.html>). A
curl command for the inventory endpoint could look like this.

curl -X POST http://:8080/pdb/query/v4 \
  -H 'Content-Type:application/json' \
  -d '{"query": "inventory[certname] { facts.path.to.fact = \"your-value\"
}" }'

The fact-content query would look similar, but you'd need to match path and
value there and it doesn't support dot notation like the inventory endpoint.

On Tue, Jul 16, 2019 at 10:16 AM Biraj Sahu  wrote:

>
> PuppetDB version- 5.2
>
> I want to retrieve list of servers with a specific role- tata_umg
>
>
>
> The json is in below format:
>
> [
>
>  {
>
>  "certname":"",
>
>  "environment":"",
>
>  "name":"_clientname",
>
>  "value":{
>
> "clientabc":{
>
>"_productname":{
>
>   "tata":{
>
>  "_instanceid":"0",
>
>  "_serverrole":[
>
> "tata_umg"
>
>  ]
>
>   }
>
>}
>
> }
>
>  }
>
>   }]
>
> Can use below 2 get requests to reterive:
>
> curl -X GET '
> http://puppetdb.aws.internal:8080/pdb/query/v4/facts/_clientname'
>
> curl -X GET 'http://puppetdb.aws.internal:8080/pdb/query/v4/facts'
> --data-urlencode 'query=["=", "name", "_clientname"]'
>
>
>
> But this gives me a json with all server's - '_clientname' and not
> specific to a certain role.
>
>
>
> Can anyone please help me update the query to make it work as per my need.
>
> --
> 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 this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/8d2e4bc6-762e-4349-ac28-e20d587d36df%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/8d2e4bc6-762e-4349-ac28-e20d587d36df%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Austin Blatt*
Associate Software Engineer
austin.bl...@puppet.com

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADVW12Mn9LhuvtmqLpxbG5BWPbvsGHJaRK6Pybywg5eHEA__7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Removing puppet-client-tools from puppet6

2019-05-20 Thread Austin Blatt 
Hi Bram,

We are in the process of retiring puppet-client-tools entirely. Shipping
puppet-client-tools was significant overhead for a package that only
contained the PuppetDB CLI. Also, in an effort to limit the number of
languages we develop in, we have rewritten the PuppetDB CLI in Ruby and
released it as a gem.

On a machine running puppet 6 I recommend installing the PuppetDB CLI via
one of the following commands (depending on which scope you've installed
Puppet in), and ensure whichever path you use for --bindir is also added to
your shell's PATH.

For Puppet installed in its system location
gem install --bindir /opt/puppetlabs/bin puppetdb_cli

For Puppet installed for the current user
gem install --bindir ~/.puppetlabs/bin puppetdb_cli

If the machine is not managed by Puppet, it is also possible to install to
your default Ruby bindir (by omitting the --bindir option entirely) and use
via the puppet-query and puppet-db commands directly.
gem install puppetdb_cli

The documentation for installing puppet-client-tools will be updated
shortly with the new gem installation steps. If you have any problems with
the new PuppetDB CLI please file a PDB ticket in Jira
<https://tickets.puppetlabs.com/> so we can get it fixed.

On Thu, May 16, 2019 at 2:54 PM Bram Vogelaar 
wrote:

> hello Molly
>
> have there been any developments with regards to (re-) publishing a puppet
> 6 compatible version of this package?
>
> Bram
>
> On Fri, 5 Apr 2019 at 00:17, Molly Waggett 
> wrote:
>
>> Hey folks!
>>
>> Unfortunately we've had to pull the puppet-client-tools packages from the
>> puppet6 package repositories. These packages were built against puppet5 and
>> are therefore incompatible with the version of OpenSSL used in puppet6.
>>
>> We will republish puppet6-compatible packages soon.
>>
>> Thanks for your understanding!
>>
>> --
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
>> --
>> 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 this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/CAFOE68A%2BbN-hKiH0H8oCfzDj5GEwc_c%2BSSSVqdpPOrLzxSyKtA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-users/CAFOE68A%2BbN-hKiH0H8oCfzDj5GEwc_c%2BSSSVqdpPOrLzxSyKtA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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 this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAGX-YaJPQrscSpwL5fnGLBxc_QzYcnvAXbqFKB61fXYeeZuaAQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAGX-YaJPQrscSpwL5fnGLBxc_QzYcnvAXbqFKB61fXYeeZuaAQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Austin Blatt*
Associate Software Engineer
austin.bl...@puppet.com

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADVW12MPnW0qg6DpaXbHirR5HX4ok366FqZ_zB%2B6BukdPsQHyQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: View all the failed executions on Puppetdb

2019-02-14 Thread Austin Blatt 
If you want all information about all failed reports you can query for
reports that have a status of failed. An example using curl would look like,

curl -X POST http://localhost:8080/pdb/query/v4 \
  -H 'Content-Type:application/json' \
  -d '{"query": "reports { status = \"failed\" }"}'

There are a few other options that might be of interest to you as well,
for example you can query for just the certname of all agents whose most
recent Puppet run failed with something like,

curl -X POST http://localhost:8080/pdb/query/v4 \
  -H 'Content-Type:application/json' \
  -d '{"query": "reports[certname] { status = \"failed\" and latest_report?
= true}"}'

You can find more docs on querying the reports endpoint for PuppetDB 5.2.7
here <https://puppet.com/docs/puppetdb/5.2/api/query/v4/reports.html>. I
hope this helps!

On Thu, Feb 14, 2019 at 8:46 AM Aditya S 
wrote:

> Sorry I forgot to add:
> puppetserver version: 5.3.7
> puppetdb version: 5.2.7
> puppet agent version: 5.5.8
>
>
> On Thursday, February 14, 2019 at 8:42:35 AM UTC-8, Aditya S wrote:
>>
>> Hi,
>>
>> Is there a way to see failed executions in PuppetDB? I can see all the
>> successful  classes in "public.catalog_resources" but is there a way to see
>> all failed executions. For example something like:
>> "Error: Could not retrieve catalog from remote server: Error 500 on
>> SERVER: Server Error: Evaluation Error: Error while evaluating a Function
>> Call, Could not find class"
>>
>> If I were not using psql but trying the REST API like
>> "/pdb/query/v4/reports"?
>>
>> Thanks!
>>
>> --
> 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 this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/14aa3fc7-1e85-4f2c-bfb3-aa2e1ed1b074%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/14aa3fc7-1e85-4f2c-bfb3-aa2e1ed1b074%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Austin Blatt*
Associate Software Engineer
austin.bl...@puppet.com

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADVW12Nq5ez2434V636V8y5XSewSFQ6cw9SikmigQKV4PRZdLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 6 removed native Nagios provider

2018-10-22 Thread Austin Blatt 
As part of the refactoring of the puppet code base, nagios resources were
moved into their own module, nagios_core
<https://forge.puppet.com/puppetlabs/nagios_core>. Installing that module
should resolve your error.

On Thu, Oct 18, 2018 at 8:45 PM comport3  wrote:

> Hi All,
>
> We are testing some Nagios stuff on Puppet 6 and it seems all the
> previously native functionality was completely removed.
>
> Is it available to be re-added via a Module? If not, why was it removed -
> technical issues, etc??
>
> Example to reproduce:
>
> (on server to be monitored, exporting it's 'nagios_host' resource)
>   @@nagios_host { $::fqdn :
> tag=> "nagios-${lookup('nagios_server')}",
> ensure => present,
> address => $facts['networking.ip'],
> use=> 'wan-host',
> hostgroups => (lookup('nagios_hostgroups', {merge => deep})).join(','),
> target => "/etc/nagios3/conf.d/puppet.d/host_${::fqdn}.cfg",
>   }
>
> (on monitoring server collecting this exported resource:
>
> *Error: Could not retrieve catalog from remote server: Error 500 on
> SERVER: Server Error: Evaluation Error: Error while evaluating a Resource
> Statement, Unknown resource type: 'nagios_host'*
>
> --
> 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 this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/0f91c67f-36f7-4c3e-ab7c-d4a98d0be144%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/0f91c67f-36f7-4c3e-ab7c-d4a98d0be144%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Austin Blatt*
Associate Software Engineer
austin.bl...@puppet.com

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADVW12O-qxdqXWxbiei%3DEDVADsJGbdS4R9vOwFkB57XXF%3Dgr%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.