Issue #4561 has been updated by Glen Ogilvie.
This feature would be really helpful. It will allow people to use
facts for things like system monitoring as well much better, when structured
data, like a list of file systems, etc, can be returned.
Any idea on when this might end up available
Issue #4561 has been updated by Erik Dalén.
eric sorenson wrote:
I've written up what I think are the latest discussion as a puppet Armature
(enhancement proposal process); i'm particularly curious to see how watchers
on this bug feel about the two proposals in the Alternatives section:
Issue #4561 has been updated by eric sorenson.
I've written up what I think are the latest discussion as a puppet Armature
(enhancement proposal process); i'm particularly curious to see how watchers on
this bug feel about the two proposals in the Alternatives section:
Issue #4561 has been updated by eric sorenson.
Priority changed from High to Normal
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561#change-74071
Author: Luke Kanies
Status: Accepted
Priority: Normal
Issue #4561 has been updated by eric sorenson.
Keywords set to backlog
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561#change-73842
Author: Luke Kanies
Status: Accepted
Priority: High
Assignee:
Category:
Issue #4561 has been updated by eric sorenson.
Target version changed from 3.0.0 to 2.0.0
Pulling this back in for facter 2.
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561#change-67460
Author: Luke Kanies
Issue #4561 has been updated by Jeff Weiss.
Target version changed from 2.1.0 to 3.0.0
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561#change-63707
Author: Luke Kanies
Status: Accepted
Priority: High
Issue #4561 has been updated by Jeff Weiss.
Target version set to 2.X
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561#change-63211
Author: Luke Kanies
Status: Accepted
Priority: High
Assignee:
Category:
Issue #4561 has been updated by Ken Barber.
Assignee deleted (Ken Barber)
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561#change-62546
Author: Luke Kanies
Status: Accepted
Priority: High
Assignee:
Issue #4561 has been updated by Walter Heck.
Wanted to add this to #3704, but that has been closed as a duplicate of this.
On the geppetto mailing list the following problem popped up, which I think is
particularly painful:
pre
It seems all references to false and true trigger a warning in
Issue #4561 has been updated by Daniel Pittman.
Target version deleted (future)
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561#change-57082
Author: Luke Kanies
Status: Accepted
Priority: High
Assignee:
Issue #4561 has been updated by Ken Barber.
Target version changed from 2.0.0 to 1.7.x
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561#change-55210
Author: Luke Kanies
Status: Accepted
Priority: High
Issue #4561 has been updated by Ken Barber.
Priority changed from Low to High
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561
Author: Luke Kanies
Status: Accepted
Priority: High
Assignee: Ken Barber
Issue #4561 has been updated by Adrien Thebo.
Priority changed from High to Low
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561
Author: Luke Kanies
Status: Code Insufficient
Priority: Low
Assignee: Adrien
Issue #4561 has been updated by Ken Barber.
In regards to using the command line tool for displaying facter output - how do
people feel about the format?
I've managed to rig up something very simply using pretty_inspect ... thereby
keeping the existing ruby-like output but allowing us to see
Issue #4561 has been updated by James Turnbull.
I think i'm okay with that - albeit I'd like to see what more and multi-layered
facts look like.
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561
Author: Luke
Issue #4561 has been updated by Ken Barber.
In that case let me do more less-contrived samples and paste them here for
people to see.
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561
Author: Luke Kanies
Issue #4561 has been updated by Ken Barber.
Here is a quick sample for network interfaces (static data - not auto
generated):
network_interfaces = {eth0=
{type=physical,
ip_address=192.168.1.1,
netmask=255.255.255.0,
mac_address=00:10:24:f4:ab:ce},
eth1=
Issue #4561 has been updated by Luke Kanies.
IMO the format has to be either json or yaml - some cross-language standard
format. Nothing else is remotely portable.
If we don't want to introduce a dependency, we could fake it with a simple
implementation of the json subset we use.
Issue #4561 has been updated by Ken Barber.
Well this is just for the visual output only. Are you more concerned about if
we ever port Facter to another language Luke? Obviously if another language
wants to fork facter and deserialize the output the --yaml/--json options can
be used.
It
Issue #4561 has been updated by Ken Barber.
For visual assessment here is a YAML snippet using network_interfaces sample
above plus some other data:
network_interfaces:
eth0:
type: physical
ip_address: 192.168.1.1
netmask: 255.255.255.0
mac_address:
Issue #4561 has been updated by Luke Kanies.
Ken Barber wrote:
Well this is just for the visual output only. Are you more concerned about if
we ever port Facter to another language Luke? Obviously if another language
wants to fork facter and deserialize the output the --yaml/--json options
Issue #4561 has been updated by Ken Barber.
Luke Kanies wrote:
I consider this capability -- easy parsing by arbitrary tools in arbitrary
languages -- to be required for every data type we produce.
So what do you think about making the default output just YAML from here on in?
The
Issue #4561 has been updated by Randall Hansen.
A good principle is that output should be human-readable by default. YAML is
quite good for this, as long as we substitute geek for human. :) That's
appropriate for our audience.
Feature #4561:
Issue #4561 has been updated by Adrien Thebo.
+1 for using YAML. It's the simplest and most portable solution from what I can
see.
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561
Author: Luke Kanies
Issue #4561 has been updated by Luke Kanies.
YAML works great for all the needs I know of.
I think JSON will be required at some point, but yaml is the best of the
available options at this point, IMO.
Feature #4561: Structured data should be supported
Issue #4561 has been updated by R.I. Pienaar.
With JSON becoming more and more prevalent is it worth considering specifically
not supporting symbols as they cause problems with JSON?
pre
{foo = bar, :foo = baz, foo = meh}.to_json
= {foo:baz,foo:meh}
/pre
Issue #4561 has been updated by Adrien Thebo.
Assignee set to Adrien Thebo
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561
Author: Luke Kanies
Status: Accepted
Priority: High
Assignee: Adrien Thebo
Issue #4561 has been updated by James Turnbull.
Target version set to 2.0.0
Feature #4561: Structured data should be supported
https://projects.puppetlabs.com/issues/4561
Author: Luke Kanies
Status: Accepted
Priority: High
Assignee:
Category: library
29 matches
Mail list logo
