[Puppet Users] How to determine best place to put external facts?

[Sean]

Hi,

I am searching for a reasonably good method to determine where I should 
drop external fact files (like yaml/json files) on an arbitrary 
unix/linux/mac system...preferably outside of puppet.  It seems different 
versions and install methods of puppet put the facter/facts.d directory in 
different places.

For example, on a unix/linux host, suppose I have a cron job that produces 
a yaml file that I want to access as a fact in some module, role or 
profile.  The cron job would need to determine where to create the file so 
that puppet can pull it as a fact.  

Should the cron job just create (if necessary) /etc/facter/facts.d and drop 
a file in there?  Will that work for most unix/linux platforms and versions 
of puppet 3 and 4?

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/0067aba0-f316-4660-bc31-ce1713fed76d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Apply

[Corey Osman]

I would suggest using a tool I wrote called the puppet debugger.  It allows you 
to write little bits of code in realtime and get the results back right away.  
It is a wonderful tool to learn the language with.  

Basically just install it and run puppet debugger, than write some puppet code. 
 

github.com/nwops/puppet-debugger 

Or online at https://www.puppet-debugger.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/3eac6702-58de-43c4-b6f7-7cd52f6589fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Order two calls of parameterized classes

[Matthew Kennedy]

You got it. Note that the arrow operators do exactly the same thing as the
before and require metaparameters so you could have add one of those to one
of the resources. Personally when a manifest has resources that are more
serial or scripty I prefer the obvious expression adding a chain of ->'d
resources had.

On Fri, Jun 2, 2017, 8:47 AM Ugo Bellavance  wrote:

> As simple as that?  Great.  I tried it and the reload did run after the
>> add, but I can't see from the logs that the reload has the add as
>> dependency.
>>
>> With your suggested change:
>>
>> Debug:
>> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Add[vhost1test91]/Zendserver::Sdk::Command[vhost_add_vhost1test_91]/Exec[zsapi_vhost_add_vhost1test_91]:
>> The container Zendserver::Sdk::Command[vhost_add_vhost1test_91] will
>> propagate my refresh event
>> Debug: Zendserver::Sdk::Command[vhost_add_vhost1test_91]: The container
>> Zendserver::Vhost::Add[vhost1test91] will propagate my refresh event
>> Debug:
>> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Add[vhost1test91]/Zendserver::Sdk::Command[vhost_reload_vhost1test_91]/Exec[zsapi_vhost_reload_vhost1test_91]/returns:
>> Exec try 1/3
>> Debug: Exec[zsapi_vhost_reload_vhost1test_91](provider=posix): Executing
>> '/usr/local/zend/bin/zs-client.sh restartPhp --target=localadmin  '
>> Debug: Executing '/usr/local/zend/bin/zs-client.sh restartPhp
>> --target=localadmin  '
>>
>> Without your change (my original code):
>>
>> Debug:
>> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Remove[vhost1test91]/Zendserver::Sdk::Command[vhost_remove_vhost1test_91]/Exec[zsapi_vhost_remove_vhost1test_91]:
>> The container Zendserver::Sdk::Command[vhost_remove_vhost1test_91] will
>> propagate my refresh event
>> Debug: Zendserver::Sdk::Command[vhost_remove_vhost1test_91]: The
>> container Zendserver::Vhost::Remove[vhost1test91] will propagate my refresh
>> event
>> Debug:
>> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Remove[vhost1test91]/Zendserver::Sdk::Command[vhost_reload_vhost1test_91]/Exec[zsapi_vhost_reload_vhost1test_91]/returns:
>> Exec try 1/3
>> Debug: Exec[zsapi_vhost_reload_vhost1test_91](provider=posix): Executing
>> '/usr/local/zend/bin/zs-client.sh restartPhp --target=localadmin  '
>> Debug: Executing '/usr/local/zend/bin/zs-client.sh restartPhp
>> --target=localadmin  '
>>
>> I don't see any difference.
>>
>>
> I think I found it:
>
> Debug:
> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1]/Zendserver::Vhost::Add[vhost1]/Zendserver::Sdk::Command[vhost_add_vhost1_80]/
> before: requires Zendserver::Sdk::Command[vhost_reload_vhost1_80]
>
>
> --
> 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/d53e3826-43fc-42ef-86cb-1a3bf4649efc%40googlegroups.com
> 
> .
> 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/CACx1-q3DVUVWbmWNze-hWoXo0G944Dq%3Dsvsi8WbHfMA83j2mTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Order two calls of parameterized classes

[Ugo Bellavance]

>
> As simple as that?  Great.  I tried it and the reload did run after the 
> add, but I can't see from the logs that the reload has the add as 
> dependency.
>
> With your suggested change:
>
> Debug: 
> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Add[vhost1test91]/Zendserver::Sdk::Command[vhost_add_vhost1test_91]/Exec[zsapi_vhost_add_vhost1test_91]:
>  
> The container Zendserver::Sdk::Command[vhost_add_vhost1test_91] will 
> propagate my refresh event
> Debug: Zendserver::Sdk::Command[vhost_add_vhost1test_91]: The container 
> Zendserver::Vhost::Add[vhost1test91] will propagate my refresh event
> Debug: 
> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Add[vhost1test91]/Zendserver::Sdk::Command[vhost_reload_vhost1test_91]/Exec[zsapi_vhost_reload_vhost1test_91]/returns:
>  
> Exec try 1/3
> Debug: Exec[zsapi_vhost_reload_vhost1test_91](provider=posix): Executing 
> '/usr/local/zend/bin/zs-client.sh restartPhp --target=localadmin  '
> Debug: Executing '/usr/local/zend/bin/zs-client.sh restartPhp 
> --target=localadmin  '
>
> Without your change (my original code):
>
> Debug: 
> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Remove[vhost1test91]/Zendserver::Sdk::Command[vhost_remove_vhost1test_91]/Exec[zsapi_vhost_remove_vhost1test_91]:
>  
> The container Zendserver::Sdk::Command[vhost_remove_vhost1test_91] will 
> propagate my refresh event
> Debug: Zendserver::Sdk::Command[vhost_remove_vhost1test_91]: The container 
> Zendserver::Vhost::Remove[vhost1test91] will propagate my refresh event
> Debug: 
> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Remove[vhost1test91]/Zendserver::Sdk::Command[vhost_reload_vhost1test_91]/Exec[zsapi_vhost_reload_vhost1test_91]/returns:
>  
> Exec try 1/3
> Debug: Exec[zsapi_vhost_reload_vhost1test_91](provider=posix): Executing 
> '/usr/local/zend/bin/zs-client.sh restartPhp --target=localadmin  '
> Debug: Executing '/usr/local/zend/bin/zs-client.sh restartPhp 
> --target=localadmin  '
>
> I don't see any difference.
>
>
I think I found it:

Debug: 
/Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1]/Zendserver::Vhost::Add[vhost1]/Zendserver::Sdk::Command[vhost_add_vhost1_80]/
before: requires Zendserver::Sdk::Command[vhost_reload_vhost1_80]
 

-- 
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/d53e3826-43fc-42ef-86cb-1a3bf4649efc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Apply

[Ugo Bellavance]

On Friday, June 2, 2017 at 9:10:00 AM UTC-4, Fairouz el ouazi wrote:
>
> HI, 
>First thank you for your response : My problem is a little bit 
> complicated . ..and  it took 's me  one week to know if puppet is the 
> device management that i m looking for  . To be more clear  ...there's an 
> existing platform that manage devices ( IOT devices ) it 's an application 
> that is  divided in many components one of them do "device management " in 
> a simple way with less functionalities for example it can't offer groupping 
> to change parameters of 10 devices at the same time ..or auto-provisioning 
> ...my job is to integrate a good device management on this platform but in 
> collaboration with the existant ... i  was thinkinh of making a puppet 
> server in the level over the existing platform and using the existant 
> device management as an agent ???
>
> Sorry my english is not that good ..but i m trying to do my best ..
>
>
No problem about the language, you're doing your best and that is the only 
thing that matters.  However, it is very hard for me to see if puppet is a 
good for you without having more information, but I think that you are the 
best person to do your tests and determine if puppet is right for you. 
 Basically, puppet can do many things on an agent (client): push files, 
install packages, start services, configure services, etc. It contains a 
number or resource types that, in turn, can be use to achieve real results 
(install and configure a LAMP stack for example, or install MySQL server 
and create a database called db1).

Ugo

-- 
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/46da62d8-0476-4102-ae81-f1af3da9a333%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Apply

[Fairouz el ouazi]

HI, 
   First thank you for your response : My problem is a little bit 
complicated . ..and  it took 's me  one week to know if puppet is the 
device management that i m looking for  . To be more clear  ...there's an 
existing platform that manage devices ( IOT devices ) it 's an application 
that is  divided in many components one of them do "device management " in 
a simple way with less functionalities for example it can't offer groupping 
to change parameters of 10 devices at the same time ..or auto-provisioning 
...my job is to integrate a good device management on this platform but in 
collaboration with the existant ... i  was thinkinh of making a puppet 
server in the level over the existing platform and using the existant 
device management as an agent ???

Sorry my english is not that good ..but i m trying to do my best ..

fairouz

Le vendredi 2 juin 2017 14:06:28 UTC+2, Ugo Bellavance a écrit :
>
>
>
> On Friday, June 2, 2017 at 4:49:13 AM UTC-4, Fairouz el ouazi wrote:
>>
>> HI, 
>>
>>I'm still a beginner in Puppet , and i want to know the advantages and 
>> in winch cases we have to use Puppet in standalone  version ?
>>All that i found is that :single host method on puppet can be the best 
>> way to get started with puppet language , and the best way to quickly 
>> develop and test manifest ? 
>>If anyone has any examples of use cases ? 
>>   THINKS ,
>>
>
> I'd say that the first step would be to create a lab to do some testing. 
> I'd also recommend buying one or a few books about the topic, this will 
> help you a lot. Have you started searching a bit by yourself?  Did you see 
> https://learn.puppet.com/category/self-paced-training?
>
> I'm not sure if I understand your questions correctly, but I don't think 
> there is a "best" way of testing.  You can write manifests on a single VM 
> and test them, but you can also setup a server quite quickly and get going 
> like that. I know that many books cover this topic. I just can't remember 
> which ones.
>
> What kind of use cases are you looking for? Do you have any business needs 
> or is it just to learn?  I suggest that you look at public modules that are 
> on the forge. It's good to be able to create manifests and modules, but 
> many needs can be fulfilled by using modules.
>

-- 
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/5249a77f-0867-48de-8d62-9c9c12015de7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Apply

[Ugo Bellavance]

On Friday, June 2, 2017 at 8:06:28 AM UTC-4, Ugo Bellavance wrote:
>
>
>
> On Friday, June 2, 2017 at 4:49:13 AM UTC-4, Fairouz el ouazi wrote:
>>
>> HI, 
>>
>>I'm still a beginner in Puppet , and i want to know the advantages and 
>> in winch cases we have to use Puppet in standalone  version ?
>>All that i found is that :single host method on puppet can be the best 
>> way to get started with puppet language , and the best way to quickly 
>> develop and test manifest ? 
>>If anyone has any examples of use cases ? 
>>   THINKS ,
>>
>
> I'd say that the first step would be to create a lab to do some testing. 
> I'd also recommend buying one or a few books about the topic, this will 
> help you a lot. Have you started searching a bit by yourself?  Did you see 
> https://learn.puppet.com/category/self-paced-training?
>
> I'm not sure if I understand your questions correctly, but I don't think 
> there is a "best" way of testing.  You can write manifests on a single VM 
> and test them, but you can also setup a server quite quickly and get going 
> like that. I know that many books cover this topic. I just can't remember 
> which ones.
>
> What kind of use cases are you looking for? Do you have any business needs 
> or is it just to learn?  I suggest that you look at public modules that are 
> on the forge. It's good to be able to create manifests and modules, but 
> many needs can be fulfilled by using modules.
>

This tutorial 
is
 
not perfect, but it's quite good: 

-- 
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/b0fa629e-ad2a-4b65-a937-f32b14b83ba4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Order two calls of parameterized classes

[Ugo Bellavance]

On Thursday, June 1, 2017 at 11:39:26 PM UTC-4, Matthew Kennedy wrote:
>
> Because puppet is declarative you can only have one instance of a resource 
> with a particular title in the catalog. This means you cannot have two 
> instances of a class in the catalog (though you can include a class 
> multiple times but it only exists in the catalog once)
>
> Luckily you do not have two instances of a class. 
>  'zendserver::sdk::command' appears to be a defined type.
>

That was on purpose :).
 

>
> Defined types generate resources. You can have multiple instances of a 
> type so long as the title is unique. This is exactly what your example 
> shows, two instances of 'zendserver::sdk::command' with two different 
> titles.
>
> Now the good part for you. Defined types contain all of their unique 
> resources.  This means that any resources that get generated by 
> 'zendserver::sdk::command' will honor the ordering metaparameters. See 
> https://docs.puppet.com/puppet/4.10/lang_defined_types.html#containment
>
> The only thing you need to do to order your commands is add a -> after the 
> closing } of the first command ie
>
> zendserver::sdk::command { "vhost_add_${vhostname}_${port}":
>   target => $target,
>   api_command=> 'vhostAdd',
>   additional_options => $additional_options,
> } ->
> zendserver::sdk::command { "vhost_reload_${vhostname}_${port}":
>   target => $target,
>   api_command=> 'restartPhp',
> }
>
> Now all resources generated by Zendserver::Sdk::Command[
> "vhost_reload_${vhostname}_${port}"] will apply /after/ the resources 
> generated by Zendserver::Sdk::Command["vhost_add_${vhostname}_${port}"]
>


As simple as that?  Great.  I tried it and the reload did run after the 
add, but I can't see from the logs that the reload has the add as 
dependency.

With your suggested change:

Debug: 
/Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Add[vhost1test91]/Zendserver::Sdk::Command[vhost_add_vhost1test_91]/Exec[zsapi_vhost_add_vhost1test_91]:
 
The container Zendserver::Sdk::Command[vhost_add_vhost1test_91] will 
propagate my refresh event
Debug: Zendserver::Sdk::Command[vhost_add_vhost1test_91]: The container 
Zendserver::Vhost::Add[vhost1test91] will propagate my refresh event
Debug: 
/Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Add[vhost1test91]/Zendserver::Sdk::Command[vhost_reload_vhost1test_91]/Exec[zsapi_vhost_reload_vhost1test_91]/returns:
 
Exec try 1/3
Debug: Exec[zsapi_vhost_reload_vhost1test_91](provider=posix): Executing 
'/usr/local/zend/bin/zs-client.sh restartPhp --target=localadmin  '
Debug: Executing '/usr/local/zend/bin/zs-client.sh restartPhp 
--target=localadmin  '

Without your change (my original code):

Debug: 
/Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Remove[vhost1test91]/Zendserver::Sdk::Command[vhost_remove_vhost1test_91]/Exec[zsapi_vhost_remove_vhost1test_91]:
 
The container Zendserver::Sdk::Command[vhost_remove_vhost1test_91] will 
propagate my refresh event
Debug: Zendserver::Sdk::Command[vhost_remove_vhost1test_91]: The container 
Zendserver::Vhost::Remove[vhost1test91] will propagate my refresh event
Debug: 
/Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Remove[vhost1test91]/Zendserver::Sdk::Command[vhost_reload_vhost1test_91]/Exec[zsapi_vhost_reload_vhost1test_91]/returns:
 
Exec try 1/3
Debug: Exec[zsapi_vhost_reload_vhost1test_91](provider=posix): Executing 
'/usr/local/zend/bin/zs-client.sh restartPhp --target=localadmin  '
Debug: Executing '/usr/local/zend/bin/zs-client.sh restartPhp 
--target=localadmin  '

I don't see any difference.

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/8ef98bc1-a184-4b78-824a-e27c2b5b2c7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Order two calls of parameterized classes

[Ugo Bellavance]

On Thursday, June 1, 2017 at 6:08:01 PM UTC-4, Pete Brown wrote:
>
> The require meta parameter will do that.
>

Ok, but how to formulate it with the variables?

-- 
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/e51022f2-9761-4357-8efc-3077ec66568a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Apply

[Ugo Bellavance]

On Friday, June 2, 2017 at 4:49:13 AM UTC-4, Fairouz el ouazi wrote:
>
> HI, 
>
>I'm still a beginner in Puppet , and i want to know the advantages and 
> in winch cases we have to use Puppet in standalone  version ?
>All that i found is that :single host method on puppet can be the best 
> way to get started with puppet language , and the best way to quickly 
> develop and test manifest ? 
>If anyone has any examples of use cases ? 
>   THINKS ,
>

I'd say that the first step would be to create a lab to do some testing. 
I'd also recommend buying one or a few books about the topic, this will 
help you a lot. Have you started searching a bit by yourself?  Did you 
see https://learn.puppet.com/category/self-paced-training?

I'm not sure if I understand your questions correctly, but I don't think 
there is a "best" way of testing.  You can write manifests on a single VM 
and test them, but you can also setup a server quite quickly and get going 
like that. I know that many books cover this topic. I just can't remember 
which ones.

What kind of use cases are you looking for? Do you have any business needs 
or is it just to learn?  I suggest that you look at public modules that are 
on the forge. It's good to be able to create manifests and modules, but 
many needs can be fulfilled by using modules.

-- 
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/f48e7211-9fa6-4a90-bacd-1e3169a7adbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Apply

[Fairouz el ouazi]

HI, 

   I'm still a beginner in Puppet , and i want to know the advantages and 
in winch cases we have to use Puppet in standalone  version ?
   All that i found is that :single host method on puppet can be the best 
way to get started with puppet language , and the best way to quickly 
develop and test manifest ? 
   If anyone has any examples of use cases ? 
  THINKS ,

-- 
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/6528477e-c5a2-46f6-81b8-02f08db423dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] List all hosts

[R.I. Pienaar]

> On 31 May 2017, at 16:05, Daniel Scott  wrote:
> 
>> On Wednesday, 31 May 2017 14:36:33 UTC+1, R.I. Pienaar wrote:
>> 
>> 
>> On Wed, May 31, 2017, at 15:33, Daniel Scott wrote: 
>> > Hi, 
>> > 
>> > I'm looking for a way to list all hosts known by a puppetserver (in 
>> > puppetdb). 
>> > 
>> > I've been using 'puppet cert list --all', however, this doesn't 
>> > necessarily 
>> > correspond to the list of hosts in puppetdb (for example, if I have to 
>> > rebuild the puppet server, and lose all the certs, but I still have the 
>> > database). 
>> > 
>> > Is there a 'puppet' command to list all known hosts? 
>> > 
>> > I know that it's possible by running a curl against the puppetdb server 
>> > itself, but it would be much cleaner if I could just run a command on the 
>> > puppetserver. 
>> 
>> Install the client tools: 
>> 
>>https://docs.puppet.com/puppetdb/4.4/pdb_client_tools.html 
>> 
>> Use PQL to query it: 
>> 
>>https://docs.puppet.com/puppetdb/4.4/api/query/examples-pql.html 
> 
> Hmm, thanks.
> 
> That's basically a wrapper around a curl, right?

Probably uses the language native http client but comes down to the same. 

It's cleaner though since you don't have to worry about all the right params 
and it has a configure etc


> 
>  
> -- 
> 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/6d6d748b-3190-447b-abd3-8296335bfa67%40googlegroups.com.
> 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/4A61E459-153D-467C-8169-2869B7761166%40devco.net.
For more options, visit https://groups.google.com/d/optout.