The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets uri. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately.
The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets {{uri}}. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately.
The plugin will take a {{config}} section where each map value is the name of a fact to lookup from PuppetDB. The plugin will gather the list of certnames from the {{query}} field as well as all the facts that are used in the {{config}} mapping and automatically make a second query to retrieve all of the necessary fact values.
If a fact isn't set for a node, the config setting for that fact should not be set.
The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets {{uri}}. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately.
The plugin will take a {{config}} section where each map value is the name of a fact to lookup from PuppetDB. The plugin will gather the list of certnames from the {{query}} field as well as all the facts that are used in the {{config}} mapping and automatically make a second query to retrieve all of the necessary fact values.
If a fact isn't set for a node, the config setting for that fact should not be set.
Make a new key under the puppetdb plugin {{db_data}}, which will look up values from puppetdb (facts endpoint for now inventory when it's open source) at the same level as config and vars etc.
The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets {{uri}}. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately.
The plugin will take a {{config}} section where each map value is the name of a fact to lookup from PuppetDB. The plugin will gather the list of certnames from the {{query}} field as well as all the facts that are used in the {{config}} mapping and automatically make a second query to retrieve all of the necessary fact values.
If a fact isn't set for a node, the config setting for that fact should not be set.
Make a new key under the puppetdb plugin {{db_datapdb_data}}, which will look up values from puppetdb (facts endpoint for now inventory when it's open source) at the same level as config and vars etc.
The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets {{uri}}. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately.
The plugin will take a {{config}} section where each map value is the name of a fact to lookup from PuppetDB. The plugin will gather the list of certnames from the {{query}} field as well as all the facts that are used in the {{config}} mapping and automatically make a second query to retrieve all of the necessary fact values.
If a fact isn't set for a node, the config setting for that fact should not be set.
Make a new key under the puppetdb plugin {{pdb_data}}, which will look up values from puppetdb (facts endpoint for now inventory when it's open source) at the same level as config and vars etc.
The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets {{uri}}. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately.
The plugin will take a {{config}} section where each map value is the name of a fact to lookup from PuppetDB. The plugin will gather the list of certnames from the {{query}} field as well as all the facts that are used in the {{config}} mapping and automatically make a second query to retrieve all of the necessary fact values.
If a fact isn't set for a node, the config setting for that fact should not be set.
Make a new key under the puppetdb plugin {{pdb_data}}, which will look up values from puppetdb (facts endpoint for now inventory when it's open source) at the same level as config and vars etc.
If name or uri is set in pdb_data don't magic set uri, otherwise do magic set uri to certname.
The PuppetDB plugin can no now be used to lookup configuration values from PuppetDB facts for the `name`, `uri`, and `config` inventory options for each target.