Jira (PUP-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-8014 Create an environment_ttl setting to clear short-lived puppet environments from memory Change By: Garrett Guillotte Summary: Create an evironment_ttl environment_ttl setting to clear short-lived puppet environments from memory Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Nick Lewis assigned an issue to Unassigned Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8031) Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8031 Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass Change By: Henrik Lindberg Assignee: Henrik Lindberg Team: Platform Core Component/s: PE Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 types Nodes and Node to puppet for tasks/plans
Title: Message Title Henrik Lindberg commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans Answers / comments: the type Nodes can be an alias for Array[Node] - its main purpose is syntactic sugar (desired by users). If more control over the content is wanted users can use Array[Node, min, max]. The only concern here is that a future UI needs to dig out the parameters where a list of nodes is supposed to be presented. Now that we have the type system available for the JVM it should be a matter of assignability to Array[Node], thus allowing us to handle more advanced cases (tuples, additional restrictions on the Node's etc.) It is good to have a general purpose URI type a Node's "free form hash" is for options so Hash[String[1], Data] is fine - don't see any real need for RichData here. the comma-separated list to Array[Node}} conversion does not really have to be made at the type level - there is always logic feeding the comma separated list of nodes to a plan or task via the functions run_plan and run_task - those functions would take a string to be "potentially comma separated list", and thus if you have URI:s for nodes with commas in them (that would be extremely rare as we are not going to use fragments and queries in the URIs that denote nodes) you would instead give an actual Array of Node or URI to the execution functions. We know that a URI is not enough to fully describe a Node, and we know a hash of options will work - it needs to be open ended because different protocols will require different options. That design could potentially be tightened by having a type associated with a scheme/protocol for the options thus enabling validation of what users give but that would be a future thing. With the additional complexity added to the multiple dispatch in the execution functions comes the price of getting a generic and large error message on type mismatch. We need to also add a custom error message for that, or new users will be baffled when making small mistakes. Add Comment
Jira (PUP-7951) agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths
Title: Message Title Moses Mendoza commented on PUP-7951 Re: agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths passed CI, here: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/1.10.x/view/Suite/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-1.10.x/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8030) Provide a setting to disable translations (create tests to verify feature)
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8030 Provide a setting to disable translations (create tests to verify feature) Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8030) Provide a setting to disable translations (create tests to verify feature)
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8030 Provide a setting to disable translations (create tests to verify feature) Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title John Duarte commented on PUP-7988 Re: resources/group/should_create test fails on fedora-26-64a This has passed puppet-agent 5.3.x CI https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/5.3.x/view/Suite/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-5.3.x/29/SLAVE_LABEL=beaker,TEST_TARGET=fedora26-64a/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8032) a node definition beats a include when the names equal
Title: Message Title Henrik Lindberg commented on PUP-8032 Re: a node definition beats a include when the names equal This is a known issue in puppet 3 (which has reached end-of-life quite some time ago), and does not occur in puppet 4 or 5. Closing this as "Won't do" as it relates to the no longer maintained Puppet 3.x version. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8008) puppet module install fails to install apt 4.2.0
Title: Message Title David Mallon commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 Jesse Scott Hi Jesse, this is turning into a major blocking issue for Modules getting our releases out for PuppetConf so Hailee and Eric are free to work with you to try to get a fix for this pushed through asap Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7983) Enable testing puppet-agent built against system openssl on RHEL in PA CI pipes
Title: Message Title Jayant Sane commented on PUP-7983 Re: Enable testing puppet-agent built against system openssl on RHEL in PA CI pipes As noted in the linked epic, the following was done to facilitate testing PA linked against openssl on RHEL platforms. 1. RHEL7: Openssl lib patch revision on rhel7 is lower than what is on centos7. PA is built on centos7 but tested on rhel7. This causes failures. Workaround: Upgrade openssl to a patch revision that is >= that on Centos7 on all RHEL7 platforms (including agent and master hosts) that get used by CI during any testing. 2. RHEL 6: It was observed that PA built against system openssl on Centos 6 works fine on RHEL6 w/o needing any openssl adjustments. Latest status : All steps till 9 in the adhoc PA CI pipeline succeed on RHEL 6 and 7 platforms for PA linked against system openssl. Cause of the failure of "Create PEZ build" step in CI is being investigated. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7983) Enable testing puppet-agent built against system openssl on RHEL in PA CI pipes
Title: Message Title Jayant Sane updated an issue Puppet / PUP-7983 Enable testing puppet-agent built against system openssl on RHEL in PA CI pipes Change By: Jayant Sane Testing PA built against system openssl thru CI has turned into quite a non-trivial exercise. First attempt resulted in some tests failing on the master host that CI sets up. Ironically, such agents have been able to get their certificate signed by the master fine when setup manually. That led to reproducing the failure using beaker locally. Testing using beaker led to a different failure during the pre-suite/setup step of PA acceptance tests.Managed to overcome that by customizing pre-suite scripts in puppet. Now need to use this custom version of puppet when launching CI. Lets see how long this goes on... All to get a PA CI test passing certificate to be able to submit PR in puppet to enable building against system openssl. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7769) Provide a setting to disable translations
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7769 Provide a setting to disable translations Change By: Eric Delaney QA Risk Assessment Reason: manual and separate ticket created for automated tests QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (FACT-1759) facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts
Title: Message Title John Duarte updated an issue Facter / FACT-1759 facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts Change By: John Duarte QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (FACT-1775) Facter fails to build /lib/tests/facts/schema.cc
Title: Message Title John Duarte updated an issue Facter / FACT-1775 Facter fails to build /lib/tests/facts/schema.cc Change By: John Duarte QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7769) Provide a setting to disable translations
Title: Message Title John Duarte updated an issue Puppet / PUP-7769 Provide a setting to disable translations Change By: John Duarte QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8008) puppet module install fails to install apt 4.2.0
Title: Message Title David Mallon updated an issue Puppet / PUP-8008 puppet module install fails to install apt 4.2.0 Change By: David Mallon Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8032) a node definition beats a include when the names equal
Title: Message Title
Pavel Pulec updated an issue
Puppet / PUP-8032
a node definition beats a include when the names equal
Change By:
Pavel Pulec
I notice that a puppet class is not included when I use the same name in the node definition. Let me explain by example:I have the following structure on puppetmaster:manifests/nodes/zimbra.pp{code:java}node /zimbra/ { include ::zimbra}{code}modules/zimbra/manifests/init.pp{code:java}class zimbra { notify {'foobar': }}{code}I have node zimbra01 where I run puppet. It runs successfully but the notify from the class zimbra is not applied /executed (actually nothing inside zimbra class).It works in two different cases WHEN when :* I change the line "include ::zimbra" to "class { '::zimbra': }"* or when I change the line "node /zimbra/ { " to "node /zimbra[0-9]/ { "Another weird thing is that when I make a syntax error in zimbra class, puppet fails due to that.It looks like a node definition '/zimbra/' interferences with the zimbra class and so it's included but not executed.I may provide more output.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Paula McMaw commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 Currently this issue is blocking Postgresql release for Puppetconf. Link to failing Jenkins job Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8032) a node definition beats a include when the names equal
Title: Message Title Pavel Pulec updated an issue Puppet / PUP-8032 a node definition beats a include when the names equal Change By: Pavel Pulec Environment: puppet v3.8.7 on both puppet server and puppet agent , CentOS 7, ruby 2.0.0p648 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8032) a node definition beats a include when the names equal
Title: Message Title
Pavel Pulec updated an issue
Puppet / PUP-8032
a node definition beats a include when the names equal
Change By:
Pavel Pulec
I notice that a puppet class is not included when I use the same name in the node definition. Let me explain by example:I have the following structure on puppetmaster:manifests/nodes/zimbra.pp{code:java}node /zimbra/ { include ::zimbra}{code}modules/zimbra/manifests/init.pp{code:java}class zimbra { notify {'foobar': }}{code}I have node zimbra01 where I run puppet. It runs successfully but notify is not applied (actually nothing inside zimbra class).It works in two different cases WHEN:* I change the line "include ::zimbra" to "class { '::zimbra': }"* * or when I change the line ' " node /zimbra/ { ' " to ' " node /zimbra[0-9]/ { ' " Another weird thing is that when I make a syntax error in zimbra class, puppet fails due to that.It looks like a node definition '/zimbra/' interferences with the zimbra class and so it's included but not executed.I may provide more output.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8032) a node definition beats a include when the names equal
Title: Message Title
Pavel Pulec updated an issue
Puppet / PUP-8032
a node definition beats a include when the names equal
Change By:
Pavel Pulec
I notice that a puppet class is not included when I use the same name in the node definition. Let me explain by example:I have the following structure on puppetmaster:manifests/nodes/zimbra.pp{code:java}node /zimbra/ { include ::zimbra}{code}modules/zimbra/manifests/init.pp{code:java}class zimbra { notify {'foobar': }}{code}I have node zimbra01 where I run puppet. It runs successfully but notify is not applied (actually nothing inside zimbra class).It works in two different cases WHEN:* I change the line ' " include ::zimbra ' " to ' " class { '::zimbra': } ' " * or when I change the line 'node /zimbra/ {' to 'node /zimbra[0-9]/ {'Another weird thing is that when I make a syntax error in zimbra class, puppet fails due to that.It looks like a node definition '/zimbra/' interferences with the zimbra class and so it's included but not executed.I may provide more output.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8032) a node definition beats a include when the names equal
Title: Message Title
Pavel Pulec updated an issue
Puppet / PUP-8032
a node definition beats a include when the names equal
Change By:
Pavel Pulec
I notice that a puppet class is not included when I use the same name in the node definition. Let me explain by example:I have the following structure on puppetmaster:manifests/nodes/zimbra.pp{code:java}node /zimbra/ { include ::zimbra}{code}modules/zimbra/manifests/init.pp{code:java}class zimbra { notify {'foobar': }}{code}I have node zimbra01 where I run puppet. It runs successfully but notify is not applied (actually nothing inside zimbra class).It works in two different cases WHEN:* I change the line "include ::zimbra" to "class { '::zimbra': }"* * or when I change the line 'node /zimbra/ {' to 'node /zimbra[0-9]/ {'Another weird thing is that when I make a syntax error in zimbra class, puppet fails due to that.It looks like a node definition '/zimbra/' interferences with the zimbra class and so it's included but not executed.I may provide more output.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8032) a node definition beats a include when the names equal
Title: Message Title
Pavel Pulec updated an issue
Puppet / PUP-8032
a node definition beats a include when the names equal
Change By:
Pavel Pulec
I notice that a puppet class is not included when I use the same name in the node definition. Let me explain by example:I have the following structure on puppetmaster:manifests/nodes/zimbra.pp{code:java}node /zimbra/ { include ::zimbra}{code}modules/zimbra/manifests /init .pp{code:java}class zimbra { notify {'foobar': }}{code}I have node zimbra01 where I run puppet. It runs successfully but notify is not applied (actually nothing inside zimbra class).It works in two different cases WHEN:* I change the line 'include ::zimbra' to 'class { '::zimbra': }'* or when I change the line 'node /zimbra/ {' to 'node /zimbra[0-9]/ {'Another weird thing is that when I make a syntax error in zimbra class, puppet fails due to that.It looks like a node definition '/zimbra/' interferences with the zimbra class and so it's included but not executed.I may provide more output.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8032) a node definition beats a include when the names equal
Title: Message Title
Pavel Pulec created an issue
Puppet / PUP-8032
a node definition beats a include when the names equal
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/06 4:13 AM
Environment:
v3.8.7 on both puppet server and puppet agent
Priority:
Normal
Reporter:
Pavel Pulec
I notice that a puppet class is not included when I use the same name in the node definition. Let me explain by example:
I have the following structure on puppetmaster:
manifests/nodes/zimbra.pp
node /zimbra/ {
include ::zimbra
}
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans Alternative proposal: Let's add the URI datatype. An instance can be assembled from the individual parts (provided as a hash) or parsed from a string (raw or encoded depending on additional argument) and make the parts available (with choice of encoded or raw form where appropriate) as instance attributes. The URI init_hash can be described as: type UriInitHash = Struct[ Optional[scheme] => String, Optional[user_info] => String, Optional[host] => String, Optional[port] => Integer[0,default], Optional[path] => String, Optional[query] => String, Optional[fragment] => String, ]
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans Given that an URI can contain commas (but a domain name cannot), perhaps we must make it semantically clear what parts of a URI that can be included? Either that, or provide some kind of escape mechanism (double quoting the URI's for instance, since they cannot be used in an URI without escaping them) when parsing the comma-separated string. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans I assume that the options "free form hash" is really a Data hash, i.e. Hash[String[1], Data]. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 types Nodes and Node to puppet for tasks/plans
Title: Message Title
Thomas Hallgren commented on PUP-8020
Re: Add data types Nodes and Node to puppet for tasks/plans
I don't understand the motivation for Nodes, Why isn't it enough to declare Array[Node] at all times where multiple nodes are desired? From the looks of it, the only motivation for the a new type with all it's bells and whistles here would be the ability to split a comma separated string. If so, why not use a function?
function parse_nodes(String[1] $nodes) >> Array[Node] {
$nodes.split(',').map |$n| { Node($n) }
}
and if it's too cumbersome to spell out the array form, use an alias:
type Nodes = Array[Node]
If we really need a Nodes data-type for other reasons, should it be parameterized? I.e. is it possible to write Nodes[1] or Nodes[0,3]?
What about assignability? Is Nodes assignable to Array[Node]? Is the opposite true? Are they equal in magnitude? Is Nodes[2,2] assignable to Tuple[Node, Node]?
Add Comment
