The best way to do this is to use puppetdb, which you can then query from
manifests using the puppetdb_query() function.
Your query would look like (untested but i think this is right...)
$nodes_array = puppetdb_query('inventory[certname] { resources { type =
"OurSystem" } }')
(You may see references to "exported resources" which accomplishes a
similar goal but IMO querying is better because it has a superset of
exported resource functionality and you don't need to know beforehand which
resources you want to mark as being 'collectable'.)
HTH
--eric0
On Wednesday, July 5, 2017 at 7:34:26 AM UTC-7, Robert Inder wrote:
>
> I'm using Puppet (3.8) to set up installations of a system for different
> clients.
>
> We have a number of servers running "live" installations,
> and others running corresponding development installations.
>
> There is a module for the system, and each node has a separate
> instance for each client that that machine is to support.
>
> I'd like to tell the development system for a given client
> where to find the corresponding "live" installation.
>
> Can I do that? Can an instance of a OurSystem resource for client
> "Edinburgh" on node "devel9" determine which other
> node also has an instance of OurSystem for "Edinburgh"?
>
> Robert.
>
>
>
>
>
>
>
--
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/2af106e9-9cc0-43fc-a381-65974f4d1959%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
