Jira (PUP-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8020 Add data type Target to puppet for tasks/plans Change By: Thomas Hallgren Summary: Add data types Nodes and Node type Target to puppet for tasks/plans Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8020 Add data type Target to puppet for tasks/plans Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8020) Add data type Target to puppet for tasks/plans
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-8020
Add data type Target to puppet for tasks/plans
Change By:
Thomas Hallgren
Currently we use a {{String}} data type (that is supposed to have a URI format) as the way to specify a node in the execution API. While this works for now, there are some things are difficult with this design:* When introspecting a plan, the data type for a parameter that accepts nodes cannot be identified when it is simply {{ String }} , or {{ Array \ [String] }} .* There are additional values (besides what is easily expressed in a URI) that users must be able to specify* There is the desire to be able to describe nodes as a comma separated list of URI host names - the parsing and handling of that (creating individual node references) is logic that should be available in a single implementationTo solve this, we should add two a new data types type {{ Node Target }} to describe a single node , and {{Nodes}} a . A collection of {{ Node Target }} that in most aspects behaves like it was an is described using {{Array\[ Node Target ]}}.A {{ Node Target }} has the following attributes:* {{ uri host }} - contains the protocol, hostname, port, user and password - the individual parts are also available as separate attributes - when constructing an instance, it is specified as either a uri, or as individual parts. (Construction from parts is clearer when author needs to construct the uri from individual values; such as looking up user/password information).* tbd - additional options that vary per protocol - probably a free form hash under an {{ options String\[1] }} attribute - but this may be designed with stronger typing if there is a registry of available protocols (that types valid options).* The constructor should accept a single string and take that to be a URI, or a hash where either uri + options are specified, or for the individual parts + options host name . The {{Nodes}} data type * has an internal list of {{ Node options }} * it is constructed from a - An optional {{ Hash\[ String }} such that a split is first made on {{,}} and each split string (s) is fed to {{Node.new(s)}}* it is constructed from an {{Array}} such that each element is an {{Init \[ Node 1 ] , Data] }} - a String or a Hash of attributes for a {{Node}} additional options that vary. The functions that take "nodes" should be updated to also accept instance of {{ Nodes Target }}, {{Node}}, or {{Array\[ Node Target ]}}. (if they are fed strings, they will create the corresponding Node {{Target}} instances).To complete the functionality, there must be a way to give {{ Node Target }}/{{ Nodes Array\[Target] }} to bolt (currently this is a URI String only). We do not want to encode all of the attributes of host {{ Node String }} into a URI instead we want a URI in string form to be a unique identifier for one node (connection only ).
Jira (PUP-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8020 Add data type Target to puppet for tasks/plans Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8020) Add data type Target to puppet for tasks/plans
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8020
Add data type Target to puppet for tasks/plans
Change By:
Henrik Lindberg
Release Notes Summary:
A new data type {{Target}} has been added to the puppet type system to allow describing a 'target node' with a host string (a host name or complete URI) and a hash of options.It is recommended that plans that take parameters that are references to nodes/hosts should use this data type for parameters that accept one or more hosts; for example {{Target}}, or {{Array\[Target]}}.
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Michael Smith commented on PUP-8020 Re: Add data type Target to puppet for tasks/plans Henrik Lindberg there are docs sub-tasks on this ticket that were never finished. Did you have a plan to do so? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Michael Smith commented on PUP-8020 Re: Add data type Target to puppet for tasks/plans This has been moved to Bolt. I believe the release notes should be revised. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Henrik Lindberg commented on PUP-8020 Re: Add data type Target to puppet for tasks/plans There are two subtasks in this ticket that are still open - I think Thomas Hallgren were going to address those, but now that types moved to Bolt, there is only need for the pre-docs. The specification should perhaps just list the names as "reserved for Bolt" as they are in the top namespace. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8020 Add data type Target to puppet for tasks/plans Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8020 Add data type Target to puppet for tasks/plans Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
