Jira (PUP-8601) agent should support rich data content negotiation

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-8601   Re: agent should support rich data content negotiation Another aspect of content negotiation is that we need to make this available to the compiler to allow users to handle update of agents more gracefully; i.e. one code path for agents that does not accept "rich data" (and therefore cannot handle Deferred etc), and another path for those that can (that is, if users want to do this with the same set of classes; which is probably the easiest). Thus, the result of content negotiation should be available and it cannot really be among the facter facts, but could possibly be placed in $facts even if it is a binding that takes place at time of communication rather than time of sending the facts. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.