Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Eric Thompson commented on PUP-8726 Re: Agent Functions - Content negotiation of rich data types to old/new agents closing in favor of pup-8601, which has more info. my questions/comments above are largely out of scope of these tickets and are recorded/reflected in Henrick's "RichData and Late Binding - Predocs" doc. 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.
Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-8726 Agent Functions - Content negotiation of rich data types to old/new agents Change By: Eric Thompson Assignee: Josh Cooper 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.
Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Henrik Lindberg commented on PUP-8726 Re: Agent Functions - Content negotiation of rich data types to old/new agents With my branch/PR it is possible to load all data types that are in Puppet. The data types in modules will not be present on the agent until we fix plugin sync to include those types. Must also fix loading data types and functions from modules for the feature to be complete. It is very much usable without those though. Regarding rich-data; I expect that to be on by default in newer agents and (naturally) off in existing. If we change "serialize as string" when rich data is written when rich-data is off then we break API since this is how it has worked earlier (and may be expected behaviour by users). However, if content type is negotiated and it says "no rich data please" then it should error IMO. Question is if it is ok to error for older agents (small risk people rely on "to_s" being called on all objects). 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.
Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Eric Thompson commented on PUP-8726 Re: Agent Functions - Content negotiation of rich data types to old/new agents Henrik Lindberg Josh Cooper what more needs to be done to resolve this? an Error when an agent connects which cannot accept rich data seems like the way to go to me. this ticket is ensuring agent/master catalog and content negotiation. do we need something similar with puppetdb? e.g.: exported "rich" resources, queries of rich data, "rich" serialized catalog storage. 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.
Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Henrik Lindberg assigned an issue to Josh Cooper Puppet / PUP-8726 Agent Functions - Content negotiation of rich data types to old/new agents Change By: Henrik Lindberg Assignee: Josh Cooper 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.
Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Henrik Lindberg commented on PUP-8726 Re: Agent Functions - Content negotiation of rich data types to old/new agents A question is what should happen when an older agent requests a catalog and the code being compiled contains rich data values. At present it would turn the rich data into strings and issue warnings. If for example the Defferred data type was used it may end up doing strange things with that value (as a string value) instead of failing. For that reason we should probably make it an error if a rich value is being serialized when content negotiation said it did not want them. 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.
Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Craig Gomes created an issue Puppet / PUP-8726 Agent Functions - Content negotiation of rich data types to old/new agents Issue Type: Task Assignee: Unassigned Created: 2018/05/14 7:18 AM Priority: Normal Reporter: Craig Gomes Required - newer masters supporting agent lookup and rich data types must be able to talk to newer agents which also support these features, and older agents that don't (content negotiation). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
