Issue #7294 has been updated by Daniel Pittman. Category set to Faces Status changed from Unreviewed to Needs Decision Assignee set to Nigel Kersten Affected Puppet version set to 2.7.0rc1
Nigel, I think this is a high priority issue, since we routinely run into problems with it. It has been around more or less forever, but has become vastly more visible to end users now that we are encouraging them to use, eg, faces built around indirected classes using the network encoding system. Also, it is a relatively pressing faces issue, since we have a whole pile of complicated, special-case code in the `puppet/application/face_base.rb` library that works around some of the issues around this (and my nervousness at what flow-on effects changing this code might have at the network layer.) ---------------------------------------- Bug #7294: Format encoding/decoding meta-bug for Faces, network, and others https://projects.puppetlabs.com/issues/7294 Author: Nick Fagerlund Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: Faces Target version: Affected Puppet version: 2.7.0rc1 Keywords: Branch: This ticket is to round up a constellation of issues around data formats. A brief overview: * The REST API doesn't use recognizable MIME formats. (issue #4456) * This appears to be because the network formats code takes the name of a format and prepends `.to_` to it. This is bad because we end up having to ask for formats like "s," and request "pson" instead of "json." (see also issue #7160) * The faces CLI uses the network formats code to render its output... except when it doesn't. (Prettyprinted json.) * Requesting nonexistant formats blows up in an opaque way. (issue #7269) * Some faces, especially indirector faces, return odd default formats. (issue #7293, e.g.) It would be nice to get to a place where users tend to get what they need by default; can expect the same formats to work on the REST API, the Faces API, and the Faces CLI; and have a sensible (text or text/plain instead of s, e.g.) set of formats that is either clearly documented or (better yet) introspectable. Once folk feel we have more concrete tickets that capture all of what we want, we can close this ticket. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
