Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Michael Smith commented on FACT-1015 Re: deprecation of 'facter --puppet' removes critically necessary functionality Other functionality we should support is dumping yaml - which should be provided by puppet facts --render_as yaml - and providing just the facts rather than the whole facts node indirector response (which puts facts in the values key). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Kylo Ginsberg commented on FACT-1015 Re: deprecation of 'facter --puppet' removes critically necessary functionality Jo Rhett gotcha, and that makes perfect sense. Given that I think I'll move this to the PUP project and adjust the summary to something like 'puppet facts' should allow retrieval of a specified fact. Once that is done, there could be a follow-on effort to further extend puppet facts to provide something like facter 3's dotted syntax for pulling out an individual element of a structured fact. That really needs to be sanity-checked for UX consistency across the various projects though, so out of scope for this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Jo Rhett commented on FACT-1015 Re: deprecation of 'facter --puppet' removes critically necessary functionality Kylo: I'm asking about the ability to get ANY fact provided through puppet pluginsync on the command line after --puppet is removed. String, structured, etc. In my experience it is very common practice to make new facts available, and then use them in shell scripts run on the host – say for cron jobs, scripts invoked by jenkins, etc. The facter 3 functionality shown above would be nice, but is nearly irrelevant without the ability to see Puppet's facts. There's only a few structured facts available by default. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title
Jo Rhett created an issue
Facter / FACT-1015
deprecation of 'facter --puppet' removes critically necessary functionality
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/05/21 11:53 PM
Priority:
Major
Reporter:
Jo Rhett
So while I understand the goal behind
FACT-96
. there's a significant loss of functionality there. I see no method of retrieving a single value, which is very highly used within external scripts which make use of puppet plugin-synced facts.
$ facter system_uptime
{seconds=532, hours=0, days=0, uptime=0:08 hours}
Note in this context, just from my personal source archives I found more than 1000 uses of this exact functionality, and I can attest to tens of thousands more uses at companies where I am not allowed to take their source offsite on my laptop.
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title
Kylo Ginsberg commented on FACT-1015
Re: deprecation of 'facter --puppet' removes critically necessary functionality
Ah I saw the comment on
FACT-96
but missed this ticket initially. So I'll ask here
Jo Rhett I didn't connect your comment to your example. Specifically, system_uptime is a built-in fact, not a plugin-synced fact. Are you asking about the ability to get an individual element of a structured fact (like system_uptime) from the command-line?
If so, with facter 3, you can use a dotted syntax on the command line, e.g.
$ ./bin/facter system_uptime
{
days = 27,
hours = 669,
seconds = 2410743,
uptime = 27 days
}
$ ./bin/facter system_uptime.days
27
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Josh Cooper commented on FACT-1015 Re: deprecation of 'facter --puppet' removes critically necessary functionality I could have sworn we already had a ticket on this, but I can't find it. Yep, the functionality is important, and something we plan on addressing before removing the --puppet option. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
