Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Duplicate
-
None
-
None
-
None
-
-
Night's Watch
-
2
Description
When you run puppet facts, you get something like:
{
|
"name": "node name the facts is for",
|
"timestamp": "when the facts were retrieved",
|
"expiration": "not sure what this is telling us but its also not a fact",
|
"values": { ..... these are the actual available facts .... }
|
}
|
This is because it's one of the "indirector faces," and it just spits back a serialized Puppet::Node::Facts object. I posit that nobody wants this: the output of puppet facts should instead be consistent with that of facter, and it should have similar options for outputting as JSON or text.
One consequence of displaying an indirector object instead of a list of facts is that it's real easy to think "name" and "timestamp" are facts, when they're actually useless noise.
Original description:
Some facts which show up when running
puppet facts
|
are not available in templates (erb):
<%= @facts['timestamp'] %> |
<%= @facts['name'] %> |
The mentioned facts do not show up in facter -p
puppet --version
|
4.3.2 |
Attachments
Issue Links
- duplicates
-
PUP-10644 Puppet facts should be able to retrieve just a list of facts if that is requested
-
- Resolved
-
- is duplicated by
-
PUP-4645 render-as string produces an object
-
- Closed
-
-
PUP-7316 Dissimilar results from puppet facts vs. facter -p
-
- Closed
-
- relates to
-
FACT-96 Deprecate 'facter --puppet'
-
- Closed
-
-
FACT-1365 Remove "Deprecated: use `puppet facts` instead" from facter --help output
-
- Closed
-
-
PUP-5934 Updated fact values should be submitted after each Puppet run
-
- Resolved
-