blob: 9d83e3d44c79abb2b5a31f74dd100feb265ca28a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
require 'puppet/indirector/face'
require 'puppet/node/facts'
Puppet::Indirector::Face.define(:facts, '0.0.1') do
copyright "Puppet Labs", 2011
license "Apache 2 license; see COPYING"
summary "Retrieve and store facts."
description <<-'EOT'
This subcommand manages facts, which are collections of normalized system
information used by Puppet. It can read facts directly from the local system
(with the default `facter` terminus), look up facts reported by other
systems, and submit facts to the puppet master.
When used with the `rest` terminus, this subcommand is essentially a front-end
to the inventory service REST API. See the inventory service documentation at
<http://docs.puppetlabs.com/guides/inventory_service.html> for more detail.
EOT
find = get_action(:find)
find.summary "Retrieve a node's facts."
find.arguments "<node_certname>"
find.returns <<-'EOT'
A hash containing some metadata and (under the "values" key) the set
of facts for the requested node. When used from the Ruby API: A
Puppet::Node::Facts object.
RENDERING ISSUES: Facts cannot currently be rendered as a string; use yaml
or json.
EOT
find.notes <<-'EOT'
When using the `facter` terminus, the host argument is ignored.
EOT
find.examples <<-'EOT'
Get facts from the local system:
$ puppet facts find x
Ask the puppet master for facts for an arbitrary node:
$ puppet facts find somenode.puppetlabs.lan --terminus rest
Query a DB-backed inventory directly (bypassing the REST API):
$ puppet facts find somenode.puppetlabs.lan --terminus inventory_active_record --mode master
EOT
get_action(:destroy).summary "Invalid for this subcommand."
get_action(:search).summary "Invalid for this subcommand."
action(:upload) do
summary "Upload local facts to the puppet master."
description <<-'EOT'
Reads facts from the local system using the `facter` terminus, then
saves the returned facts using the rest terminus.
EOT
returns "Nothing."
notes <<-'EOT'
This action requires that the puppet master's `auth.conf` file
allow save access to the `facts` REST terminus. Puppet agent does
not use this facility, and it is turned off by default. See
<http://docs.puppetlabs.com/guides/rest_auth_conf.html> for more details.
EOT
examples <<-'EOT'
Upload facts:
$ puppet facts upload
EOT
render_as :yaml
when_invoked do |options|
Puppet::Node::Facts.indirection.terminus_class = :facter
facts = Puppet::Node::Facts.indirection.find(Puppet[:certname])
Puppet::Node::Facts.indirection.terminus_class = :rest
Puppet::Node::Facts.indirection.save(facts)
Puppet.notice "Uploaded facts for '#{Puppet[:certname]}'"
nil
end
end
end
|
