Jira (PUP-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto commented on PUP-5659 Re: Puppet master does not fail catalog on unexisting resource in resource parameter Our Puppet tests compile lots of catalogs. The pain is that some easy mistakes are not found due to this. 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-6492) Reports are not stored for current node
Title: Message Title Julien Pivotto created an issue Puppet / PUP-6492 Reports are not stored for current node Issue Type: Bug Assignee: Unassigned Components: Puppet Server Created: 2016/07/12 12:57 AM Priority: Normal Reporter: Julien Pivotto In a 4 nodes environment, When Running Puppet agent --test, with report = true and reports = store in the directory /opt/puppetlabs/puppet/cache/reports I only see reports for the 3 nodes that are NOT the puppetserver On the Puppet server, the agent reports for the server host itself are not saved in /opt/puppetlabs/puppet/cache/reports Add Comment
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Julien Pivotto commented on PUP-6321 Re: undef in custom type autorequire value causes error in Puppet 4.5.0 Is this a bug of Puppet or the module? We fixed that in voxpupuli-corosync: https://github.com/voxpupuli/puppet-corosync/pull/258 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title
Julien Pivotto commented on PUP-6251
Re: Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
No, Eric Thompson [] is Array[0,0] and {{ {} }} is Hash[0,0]
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Henrik Lindberg juste on extra thing: if we allow Array[1,2], why would'nt we allow Array[1] as well? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Okay. I guess that if it was by design it would have been better to postpone this until puppet 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Will be also support notations like Array[1,1] ? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Henrik Lindberg Maybe rephrasing of the RN can also be done: In conjunction with this change, it is now also illegal to specify an element (or key/value) type when also specifying empty. For instance, Array[Integer, 0, 0] is now illegal. It gives the felling that Array[Integer, 0, 0] is failing by design. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Impossible to easily check for empty arrays Henrik Lindberg I mean that trying Array[0,0] like in the release notes does not work Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Impossible to easily check for empty arrays We also need to make Array[0,0] work Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}h2. Non technical problems# I would not expect such a change in a _minor (.z) release_# This change does not make sense because it is a valid usecase (e.g when the upper limit is a variable) to have a type.h2. Technical problemsh3. To me, the following statements are true{code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code}h3. Alternative writing does not work{code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen{code}So there is NO workaround to get the feature working again.h3. Impossible to have a variable as length{code}$test = assert_type(Array[ Integer, $min,$max],[]){code}will noly work with max > 0. Hence an extra {{if}} in the code etc etc
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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.goo
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Impossible to easily check for empty arrays I do agree with PUP-6089 . It does not make sense to display a type for empty arrays. But the extra mile of not allowing a type is too much. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}h2. Problems: Non technical problems # I would not expect such a change in a _minor (.z) release_# Array[0,0] does not work# This change does not make sense. h2. Technical problemsh3. To me, the following statements are true : {code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code} Another bug: h3. Alternative writing does not work {code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen{code}So there is NO workaround to get the feature working again. h3. Impossible to have a variable as length{code}$test = assert_type(Array[$min,$max],[]){code}will noly work with max > 0. Hence an extra {{if}} in the code etc etc
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 mo
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}h2. Non technical problems# I would not expect such a change in a _minor (.z) release_# This change does not make sense because it is a valid usecase (e . g when the upper limit is a variable) to have a type. h2. Technical problemsh3. To me, the following statements are true{code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code}h3. Alternative writing does not work{code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen{code}So there is NO workaround to get the feature working again.h3. Impossible to have a variable as length{code}$test = assert_type(Array[$min,$max],[]){code}will noly work with max > 0. Hence an extra {{if}} in the code etc etc
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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.co
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}h2. Problems:# I would not expect such a change in a _minor (.z) release_# Array[0,0] does not work# This change does not make sense.To me, the following statements are true:{code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code}Another bug:{code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen .low.cert.mil.be {code}So there is NO workaround to get the feature working again.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote} 2 things here h2. Problems :# I would not expect such a change in a _minor (.z) release_# Array[0,0] does not work# This change does not make sense.To me, the following statements are true:{code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code} Another bug:{code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen.low.cert.mil.be{code}So there is NO workaround to get the feature working again.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}2 things here:# I would not expect such a change in a _minor (.z) release_# This change does not make sense.To me, the following statements are true:{code:puppet}[] =~ Array[String , 0, 0 ][] =~ Array[Integer , 0, 0 ]{code} With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}2 things here:# I would not expect such a change in a _minor (.z) release_# This change does not make sense.To me , the following statements are true :{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}2 things here: 1. # I would not expect such a change in a _minor (.z) release_ 2. # This change does not make sense.To me:{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the followinq following :{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}2 things here:1. I would not expect such a change in a minor _minor (.z) release release_ 2. This change does not make sense.To me:{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the followinq:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error: {quote} Error while evaluating a '[]' _expression_, An empty collection may not specify an element type {quote} 2 things here:1. I would not expect such a change in a minor (.z) release2. This change does not make sense.To me:{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the followinq:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:Error while evaluating a '[]' _expression_, An empty collection may not specify an element type2 things here:1. I would not expect such a change in a minor (.z) release2. This change does not make sense.To me:{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that ` {{ Array[String] ` }} should always be ` {{ Array[String,1] ` }} . It sounds not great. ` {{ Array[String,1] ` }} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the followinq: ``` {code: puppet } if $nodes =~ Array[Data,0,0] ``` {code} I get the following error:Error while evaluating a '[]' _expression_, An empty collection may not specify an element type2 things here:1. I would not expect such a change in a minor (.z) release2. This change does not make sense.To me: ``` {code: puppet } [] =~ Array[String][] =~ Array[Integer] ``` {code} With that change, it implies that `Array[String]` should always be `Array[String,1]`. It sounds not great. `Array[String,1]` should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-6251 Impossible to easily check for empty arrays Change By: Julien Pivotto Since 4.4.2 it is impossible to do the followinq: ```puppet if $nodes =~ Array[Data,0,0] ``` I get the following error:Error while evaluating a '[]' _expression_, An empty collection may not specify an element type2 things here:1. I would not expect such a change in a minor (.z) release2. This change does not make sense.To me: ```puppet [] =~ Array[String][] =~ Array[Integer] ``` With that change, it implies that ` Array[String] ` should always be ` Array[String,1] ` . It sounds not great. `Array[String,1]` should be enforced by style guides, not like this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto created an issue Puppet / PUP-6251 Impossible to easily check for empty arrays Issue Type: Bug Affects Versions: PUP 4.4.2 Assignee: Unassigned Components: Language Created: 2016/05/02 4:44 AM Priority: Normal Reporter: Julien Pivotto Since 4.4.2 it is impossible to do the followinq: if $nodes =~ Array[Data,0,0] I get the following error: Error while evaluating a '[]' _expression_, An empty collection may not specify an element type 2 things here: 1. I would not expect such a change in a minor (.z) release 2. This change does not make sense. To me: [] =~ Array[String] [] =~ Array[Integer] With that change, it implies that Array[String] should always be Array[String,1]. It sounds not great.
Jira (PUP-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto commented on PUP-6045 Re: postrun_command should run after reports and summaries Yeah I have a workaround as well, I use a systemd unit to run puppet, and I use ExecPostStart. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto commented on PUP-6045 Re: postrun_command should run after reports and summaries TBH I started to wrote a report processor to do that but those are only possible on puppet apply and puppet server. So, portreport_command or client_reports config variable? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-6045 postrun_command should run after reports and summaries Change By: Julien Pivotto Component/s: Catalog Application Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-6045 postrun_command should run after reports and summaries Change By: Julien Pivotto Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto created an issue Puppet / PUP-6045 postrun_command should run after reports and summaries Issue Type: Bug Assignee: Unassigned Created: 2016/03/11 2:56 AM Priority: Normal Reporter: Julien Pivotto From: https://projects.puppetlabs.com/issues/8195 by R.I.Pienaar At present the postrun_command is being run before the reports are sent and therefore also before they are stored locally in lastrunfile and lastrunreport. It would be great to change that behaviour so that postrun commands have acces to the reports file. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-4669) Varargs support for "args by name" calls to user defined resource types and EPP templates
Title: Message Title Julien Pivotto commented on PUP-4669 Re: Varargs support for "args by name" calls to user defined resource types and EPP templates https://www.devco.net/archives/2016/02/28/the-resource-wrapper-pattern-in-puppet-4.php Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1343) Open Source and release the toolchain
Title: Message Title Julien Pivotto commented on FACT-1343 Re: Open Source and release the toolchain Matthew Gyurgyik I will make a second ticket for this Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDOC-43) Allow more advanced formatting in parameters descriptions
Title: Message Title Julien Pivotto commented on PDOC-43 Re: Allow more advanced formatting in parameters descriptions Current we do not allow any formatting. I wanted to write the description in markdown directly. My main usecase was links. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDOC-43) Allow more advanced formatting in parameters descriptions
Title: Message Title Julien Pivotto commented on PDOC-43 Re: Allow more advanced formatting in parameters descriptions Well the issue is simple: it was about being able to have formatting in parameters description (bold, links...): @param foo enables foo *warning: a super warning* I gave up because no progress was made for months and I ran into several issues. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run
Title: Message Title Julien Pivotto commented on PUP-5891 Re: Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run We could use Notice: /Stage[main]/Main/Refreshme[test]/Exec[This is not executed]: Triggered 'refresh' from 1 events (notrun) Or add a /Notice: /Stage[main]/Main/Refreshme[test]/Exec[This is executed]/returns: executed successfully Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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
Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5891 Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run Change By: Julien Pivotto Summary: Impossible to see the differencd difference in the logs between a refreshed exec that has run and one that has not run Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5891) Impossible to see the differencd in the logs between a refreshed exec that has run and one that has not run
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5891 Impossible to see the differencd in the logs between a refreshed exec that has run and one that has not run Change By: Julien Pivotto Summary: Impossible to see the different differencd in the logs between a refreshed exec that has run and one that has not run Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5891) Impossible to see the different in the logs between a refreshed exec that has run and one that has not run
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5891 Impossible to see the different in the logs between a refreshed exec that has run and one that has not run Change By: Julien Pivotto Summary: Impossible to see the different in the logs between a refreshed exec that has run and one that has not run Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5891) Impossible to see the different between a refreshed exec that has run and one that has not run
Title: Message Title
Julien Pivotto created an issue
Puppet / PUP-5891
Impossible to see the different between a refreshed exec that has run and one that has not run
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/02/12 4:38 AM
Priority:
Normal
Reporter:
Julien Pivotto
Consider the following code:
define refreshme {
exec {
'This is not executed':
creates => '/tmp',
command => '/bin/false',
Jira (PUP-5881) Support "provides" in Metadata.json
Title: Message Title
Julien Pivotto created an issue
Puppet / PUP-5881
Support "provides" in Metadata.json
Issue Type:
Bug
Assignee:
Unassigned
Components:
Modules
Created:
2016/02/11 6:47 AM
Priority:
Normal
Reporter:
Julien Pivotto
The warnings added by the latest versions are intrusive and annoying when you do not use the mentioned modules.
e.g I want to use the mymysql module instead of puppetlabs-mysql.
metadata.json should accept a field "provides", to tell puppet that it supports the same API and functionalities of other modules.
example:
"provides": [
{"name":"puppetlabs-puppetdb","version":"2.0.0"}
Jira (PUP-5880) Support optional dependencies in Metadata.json
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5880
Support optional dependencies in Metadata.json
Change By:
Julien Pivotto
I am trying the latest agent release and warnings have been added when modules dependencies are missing.However that message is not relevant because I do not use the features of those so-called dependencies.{code}├─┬ puppetlabs-puppetdb (v5.0.0)│ ├── UNMET DEPENDENCY puppetlabs-postgresql (>= 4.0.0 <5.0.0)│ ├── UNMET DEPENDENCY puppetlabs-firewall (>= 1.1.3 <2.0.0){code}{code}├─┬ spotify-puppetexplorer (v1.0.1)│ ├── UNMET DEPENDENCY puppetlabs-apt (>= 1.0.0)│ └─┬ puppetlabs-apache (v1.8.0)│ ├── puppetlabs-stdlib (v4.11.0)│ └── puppetlabs-concat (v2.1.0){code}I do not use pgsql or the firewall and I only have CentOS machines.We should be able to make a difference between optional and mandatory puppetmodules in metadata.json. Wanted behaviour:Optional dependency is missing: do nothingOptional dependency is present: do nothingOptional dependency is present but its version conflicts with the one from metadata.json: warn the user
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5880) Support optional dependencies in Metadata.json
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5880
Support optional dependencies in Metadata.json
Change By:
Julien Pivotto
I am trying the latest agent release and warnings have been added when modules dependencies are missing.However that message is not relevant because I do not use the features of those so-called dependencies.{code}├─┬ puppetlabs-puppetdb (v5.0.0)│ ├── UNMET DEPENDENCY puppetlabs-postgresql (>= 4.0.0 <5.0.0)│ ├── UNMET DEPENDENCY puppetlabs-firewall (>= 1.1.3 <2.0.0){code}{code}├─┬ spotify-puppetexplorer (v1.0.1)│ ├── UNMET DEPENDENCY puppetlabs-apt (>= 1.0.0)│ └─┬ puppetlabs-apache (v1.8.0)│ ├── puppetlabs-stdlib (v4.11.0)│ └── puppetlabs-concat (v2.1.0){code}I do not use pgsql or the firewall and I only have CentOS machines.We should be able to make a difference between optional and mandatory puppetmodules in metadata.json.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5880) Support optional dependencies in Metadata.json
Title: Message Title Julien Pivotto created an issue Puppet / PUP-5880 Support optional dependencies in Metadata.json Issue Type: Bug Assignee: Unassigned Components: Modules Created: 2016/02/11 6:25 AM Priority: Normal Reporter: Julien Pivotto Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you
Jira (PUP-5839) Potential regressions in relationship validation
Title: Message Title Julien Pivotto commented on PUP-5839 Re: Potential regressions in relationship validation As PUP-5659 has been reverted, can we close this ticket and continue the discussion there? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5839) Potential regressions in relationship validation
Title: Message Title Julien Pivotto commented on PUP-5839 Re: Potential regressions in relationship validation IMO we need to be backward compatible about the aliases, because it makes sense (maybe some people use them to stub 3rd party classes or resources) For the file resource, we need to look further because some custom types and providers might behave in the same way. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5839) Potential regressions in relationship validation
Title: Message Title Julien Pivotto commented on PUP-5839 Re: Potential regressions in relationship validation Kenneth Barber I think we need a new bug for this? Like: metaparameters relationship are less explicit than direct relationships? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5839) Potential regressions in relationship validation
Title: Message Title
Julien Pivotto commented on PUP-5839
Re: Potential regressions in relationship validation
Please note that the following already create errors now:
a)
notify { 'a': alias => 'b'}
notify { 'c':}
Notify['c'] -> Notify['b']
Returns: Error: Could not find resource 'Notify[b]' for relationship from 'Notify[c]' on node nitrogen
and b)
file{ '/tmp/': }
notify { 'a': }
Notify['a'] -> File['/tmp']
Error: Could not find resource 'File[/tmp]' for relationship from 'Notify[a]' on node nitrogen
Jira (FACT-1343) Open Source and release the toolchain
Title: Message Title
Julien Pivotto updated an issue
Facter / FACT-1343
Open Source and release the toolchain
Change By:
Julien Pivotto
It would be great if you would release the buildchain used to build facter 3.x on EL (Spec files), to enable community rebuild of those packages the buildchain and the facter package .https://github.com/puppetlabs/facter/blob/a8b1cc4e481c3acc179eb1c70b3706af8998df22/ext/redhat/facter.spec.erb#L36-L41{code}BuildRequires: pl-gcc >= 4.8.2-4BuildRequires: pl-cmake >= 3.2.2-1BuildRequires: pl-libboost-devel >= 1.55.0-4BuildRequires: pl-libboost-static >= 1.55.0-4BuildRequires: pl-libyaml-cpp-devel >= 0.5.1-5BuildRequires: pl-libyaml-cpp-static >= 0.5.1-5{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-1343) Open Source and release the toolchain
Title: Message Title Julien Pivotto created an issue Facter / FACT-1343 Open Source and release the toolchain Issue Type: Bug Affects Versions: FACT 3.x Assignee: Unassigned Components: Community Created: 2016/02/07 11:09 PM Priority: Normal Reporter: Julien Pivotto It would be great if you would release the buildchain used to build facter 3.x on EL (Spec files), to enable community rebuild of those packages. https://github.com/puppetlabs/facter/blob/a8b1cc4e481c3acc179eb1c70b3706af8998df22/ext/redhat/facter.spec.erb#L36-L41 BuildRequires: pl-gcc >= 4.8.2-4 BuildRequires: pl-cmake >= 3.2.2-1
Jira (PUP-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title
Julien Pivotto commented on PUP-4669
Re: Varargs support for (defined) types (and possibly classes)
Can we please NOT implement this.
This can be achieved like this anyway:
define http2https_vhost (
$servername= $name,
Optional[Array[String]] $serveraliases,
Optional[Hash] $extra_vhost_options = undef,
) {
...
apache::vhost ( "https-${servername}":
servername => $servern
Jira (PUP-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto commented on PUP-5659 Re: Puppet master does not fail catalog on unexisting resource in resource parameter Henrik Lindberg If there is a usercase then the other check is wrong? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto commented on PUP-5659 Re: Puppet master does not fail catalog on unexisting resource in resource parameter This is not a regression, it has been there for a while (at least puppet 3.5,maybe sooner) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5607) Puppetmaster uses its own facts with providers
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5607 Puppetmaster uses its own facts with providers Change By: Julien Pivotto Component/s: Catalog Application Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5659 Puppet master does not fail catalog on unexisting resource in resource parameter Change By: Julien Pivotto Comment: It is a regression between Puppet 3.4.0 and 3.5.0https://travis-ci.org/roidelapluie/PUP-5659 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5659 Puppet master does not fail catalog on unexisting resource in resource parameter Change By: Julien Pivotto Comment: It is not a regression, it has always been like thishttps://travis-ci.org/roidelapluie/PUP-5659 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto commented on PUP-5659 Re: Puppet master does not fail catalog on unexisting resource in resource parameter It is a regression between Puppet 3.4.0 and 3.5.0 https://travis-ci.org/roidelapluie/PUP-5659 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto commented on PUP-5659 Re: Puppet master does not fail catalog on unexisting resource in resource parameter It is not a regression, it has always been like this https://travis-ci.org/roidelapluie/PUP-5659 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5659
Puppet master does not fail catalog on unexisting resource in resource parameter
Change By:
Julien Pivotto
The behavior of Resources in require => parameter and in relations is different.When compiling the catalog of the two following nodes, the first one fails on the _client_ side, and the second one on the _server_ side. This is very annoying because you think that the catalog can be applied successfully (e.g if you test using puppet master compile).{code:puppet}node missing1 { notify {'a':require => Notify['b'], }}node missing2 { notify {'a': } Notify['b'] -> Notify['a']}{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5607) Puppetmaster uses its own facts with providers
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5607
Puppetmaster uses its own facts with providers
Change By:
Julien Pivotto
BACKGROUND: h2. Background * Testsuite for our internal ENC uses Puppet Master command to compile catalogs and test its content* On my laptop I am not running a distribution known by facter so the OperatingSystem fact is empty.* With commit https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem can no longer be empty:{code}Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{code} BUT IT SHOULD NOT BE EMPTY: h2. The problem It should not fail because operatingsystem fact is provided to the puppetmaster in a yaml fact for that node. Here is the command I use to compile the catalog:{code}/home/roidelapluie/dev/ruby/bin/puppet master --modulepath=../puppet/modules --environmentpath=src/test/resources/environment --node_terminus=exec --external_nodes=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/enc.sh --yamldir=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml --logdest=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/catalog-fadel.stammwuckert.biz-log.json --compile=fadel.stammwuckert.biz{code}I attach the /tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/facts/fadel.stammwuckert.biz.yaml to thit ticket. It clearly contains the Operatingsystem fact. THE PROBLEM: Looks like when Puppetmaster compiles a catalog, it uses the local facts in https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem and not the facts of the client (provided in the yaml file) ADDITIONAL INFO: h2. Additional info Other things that depend of facts work use the content of yaml facts (in *.pp files) POSSIBLE IMPACT: h2. Possible impact A Debian Puppetmaster could tell all the other clients that the init provider is not available even if other clients supports it.
Add Comment
Jira (PUP-5607) Puppetmaster uses its own facts with providers
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5607
Puppetmaster uses its own facts with providers
Change By:
Julien Pivotto
BACKGROUND:* Testsuite for our internal ENC uses Puppet Master command to compile catalogs and test its content* On my laptop I am not running a distribution known by facter so the OperatingSystem fact is empty.* With commit https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem can no longer be empty:{code}Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{code}BUT IT SHOULD NOT BE EMPTY:Here is the command I use to compile the catalog:{code}/home/roidelapluie/dev/ruby/bin/puppet master --modulepath=../puppet/modules --environmentpath=src/test/resources/environment --node_terminus=exec --external_nodes=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/enc.sh --yamldir=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml --logdest=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/catalog-fadel.stammwuckert.biz-log.json --compile=fadel.stammwuckert.biz{code}I attach the /tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/facts/fadel.stammwuckert.biz.yaml to thit ticket. It clearly contains the Operatingsystem fact.THE PROBLEM:Looks like when Puppetmaster compiles a catalog, it uses the local facts in https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem and not the facts of the client (provided in the yaml file)ADDITIONAL INFO:Other things that depend of facts work use the content of yaml facts (in *.pp files) POSSIBLE IMPACT:A Debian Puppetmaster could tell all the other clients that the init provider is not available even if other clients supports it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5607) Puppetmaster uses its own facts with providers
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5607
Puppetmaster uses its own facts with providers
Change By:
Julien Pivotto
BACKGROUND:* Testsuite for our internal ENC uses Puppet Master command to compile catalogs and test its content* On my laptop I am not running a distribution known by facter so the OperatingSystem fact is empty.* With commit https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem can no longer be empty:{code}Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{code}BUT IT SHOULD NOT BE EMPTY:Here is the command I use to compile the catalog:{code}/home/roidelapluie/dev/ruby/bin/puppet master --modulepath=../puppet/modules --environmentpath=src/test/resources/environment --node_terminus=exec --external_nodes=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/enc.sh --yamldir=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml --logdest=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/catalog-fadel.stammwuckert.biz-log.json --compile=fadel.stammwuckert.biz{code}I attach the /tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/facts/fadel.stammwuckert.biz.yaml to thit ticket. It clearly contains the Operatingsystem fact.THE PROBLEM:Looks like when Puppetmaster compiles a catalog, it uses the local facts in https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem and not the facts of the client (provided in the yaml file ) ADDITIONAL INFO:Other things that depend of facts work use the content of yaml facts (in *.pp files)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5607) Puppetmaster uses its own facts with providers
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5607
Puppetmaster uses its own facts with providers
Change By:
Julien Pivotto
BACKGROUND:* Testsuite for our internal ENC uses Puppet Master command to compile catalogs and test its content* On my laptop I am not running a distribution known by facter so the OperatingSystem fact is empty.* With commit https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem can no longer be empty:{code}Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{code}BUT IT IS SHOULD NOT BE EMPTY:Here is the command I use to compile the catalog:{code}/home/roidelapluie/dev/ruby/bin/puppet master --modulepath=../puppet/modules --environmentpath=src/test/resources/environment --node_terminus=exec --external_nodes=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/enc.sh --yamldir=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml --logdest=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/catalog-fadel.stammwuckert.biz-log.json --compile=fadel.stammwuckert.biz{code}I attach the /tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/facts/fadel.stammwuckert.biz.yaml to thit ticket. It clearly contains the Operatingsystem fact.THE PROBLEM:Looks like when Puppetmaster compiles a catalog, it uses the local facts in https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem and not the facts of the yaml fileADDITIONAL INFO:Other things that depend of facts work use the content of yaml facts (in *.pp files)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5607) Puppetmaster uses its own facts with providers
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5607 Puppetmaster uses its own facts with providers Change By: Julien Pivotto Attachment: fadel.stammwuckert.biz.yaml Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5607) Puppetmaster uses its own facts with providers
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5607
Puppetmaster uses its own facts with providers
Change By:
Julien Pivotto
BACKGROUND:* Testsuite for our internal ENC uses Puppet Master command to compile catalogs and test its content* On my laptop I am not running a distribution known by facter so the OperatingSystem fact is empty.* With commit https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem can no longer be empty:{code}Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{code}BUT IT IS NOT EMPTY:Here is the command I use to compile the catalog:{code}/home/roidelapluie/dev/ruby/bin/puppet master --modulepath=../puppet/modules --environmentpath=src/test/resources/environment --node_terminus=exec --external_nodes=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/enc.sh --yamldir=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml --logdest=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/catalog-fadel.stammwuckert.biz-log.json --compile=fadel.stammwuckert.biz{code}I attach the /tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/facts/fadel.stammwuckert.biz.yaml to thit ticket. It clearly contains the Operatingsystem fact.THE PROBLEM:Looks like when Puppetmaster compiles a catalog, it uses the local facts in https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem and not the facts of the yaml file ADDITIONAL INFO:Other things that depend of facts work use the content of yaml facts (in *.pp files)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5607) Puppetmaster uses its own facts with providers
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5607
Puppetmaster uses its own facts with providers
Change By:
Julien Pivotto
BACKGROUND:* Testsuite for our internal ENC uses Puppet Master command to compile catalogs and test its content* On my laptop I am not running a distribution known by facter so the OperatingSystem fact is empty.* With commit https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem can no longer be empty:{code}Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{code}BUT IT IS NOT EMPTY:Here is the command I use to compile the catalog:{code}/home/roidelapluie/dev/ruby/bin/puppet master --modulepath=../puppet/modules --environmentpath=src/test/resources/environment --node_terminus=exec --external_nodes=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/enc.sh --yamldir=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml --logdest=/tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/catalog-fadel.stammwuckert.biz-log.json --compile=fadel.stammwuckert.biz{code}I attach the /tmp/pytest-of-roidelapluie/pytest-8/test_cpu_dependent_parameters_0/yaml/facts/fadel.stammwuckert.biz.yaml to thit ticket. It clearly contains the Operatingsystem fact.THE PROBLEM:Looks like when Puppetmaster compiles a catalog, it uses the local facts in https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016 operatingsystem and not the facts of the yaml file
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5607) Puppetmaster uses its own facts with providers
Title: Message Title Julien Pivotto created an issue Puppet / PUP-5607 Puppetmaster uses its own facts with providers Issue Type: Bug Assignee: Unassigned Created: 2015/12/14 4:51 AM Priority: Normal Reporter: Julien Pivotto Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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
Jira (PUP-5606) puppet help does not display anything
Title: Message Title Julien Pivotto commented on PUP-5606 Re: puppet help does not display anything I have found the issue: I do not have the YARD gem installed but I have puppetlabs-strings. So the bug it that puppet help fails silently if ruby throwns an exception. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5606) puppet help does not display anything
Title: Message Title Julien Pivotto commented on PUP-5606 Re: puppet help does not display anything Could be due to PDOC-58 .. updating the strings module Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5606) puppet help does not display anything
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5606
puppet help does not display anything
Change By:
Julien Pivotto
{code}[root@fna100 ~]# /opt/puppetlabs/puppet/bin/puppet help[root@fna100 ~]# {code}{code}[root@fna100 ~]# /opt/puppetlabs/puppet/bin/puppet help --debugDebug: Runtime environment: puppet_version=4.3.1, ruby_version=2.1.7, run_mode=user, default_encoding=UTF-8Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'na' (ttl = 0 sec)Debug: Evicting cache entry for environment 'myenv'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment
Jira (PUP-5606) puppet help does not display anything
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5606
puppet help does not display anything
Change By:
Julien Pivotto
{code}[root@fna100 ~]# /opt/puppetlabs/puppet/bin/puppet help[root@fna100 ~]# {code}{code}[root@fna100 ~]# /opt/puppetlabs/puppet/bin/puppet help --debugDebug: Runtime environment: puppet_version=4.3.1, ruby_version=2.1.7, run_mode=user, default_encoding=UTF-8Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'na' (ttl = 0 sec)Debug: Evicting cache entry for environment 'myenv'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment
Jira (PUP-5606) puppet help does not display anything
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5606
puppet help does not display anything
Change By:
Julien Pivotto
{code}[root@fna100 ~]# /opt/puppetlabs/puppet/bin/puppet help[root@fna100 ~]# {code}{code}[root@fna100 ~]# /opt/puppetlabs/puppet/bin/puppet help --debugDebug: Runtime environment: puppet_version=4.3.1, ruby_version=2.1.7, run_mode=user, default_encoding=UTF-8Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'na' (ttl = 0 sec)Debug: Evicting cache entry for environment 'myenv'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Loading vendored Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment
Jira (PUP-5606) puppet help does not display anything
Title: Message Title Julien Pivotto created an issue Puppet / PUP-5606 puppet help does not display anything Issue Type: Bug Assignee: Unassigned Created: 2015/12/14 1:34 AM Priority: Normal Reporter: Julien Pivotto Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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.c
Jira (PUP-5606) puppet help does not display anything
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5606 puppet help does not display anything Change By: Julien Pivotto Affects Version/s: PUP 4.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5599) Add resource type length to validation error output of
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5599 Add resource type length to validation error output of Change By: Julien Pivotto Summary: Add resource type length to validation error output of Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output of Function Calls
Title: Message Title Julien Pivotto commented on PUP-5599 Re: Add resource type length to validation error output of Function Calls I was running an 4.2 version of puppet, this was fixed in 4.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output of Function Calls
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5599 Add resource type length to validation error output of Function Calls Change By: Julien Pivotto Affects Version/s: PUP 4.3.1 Affects Version/s: PUP 4.2.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output of Function Calls
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5599 Add resource type length to validation error output of Function Calls Change By: Julien Pivotto Summary: Add resource type length to validation error output of Function Calls Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5599 Add resource type length to validation error output Change By: Julien Pivotto Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output
Title: Message Title
Julien Pivotto created an issue
Puppet / PUP-5599
Add resource type length to validation error output
Issue Type:
Bug
Affects Versions:
PUP 4.3.1
Assignee:
Unassigned
Components:
Language
Created:
2015/12/11 7:25 AM
Priority:
Normal
Reporter:
Julien Pivotto
When the compilation fails because of the lenght of a String not being correct, it would be great to see that in the output.
PP file:
with ('Fooo',) | String[6,10] $foo | {}
Jira (FACT-620) windows facter $::osfamily and $::kernel output inconsistent vs other platforms
Title: Message Title Julien Pivotto commented on FACT-620 Re: windows facter $::osfamily and $::kernel output inconsistent vs other platforms Indeed, very bad idea to change this. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-852) Add support for systemd and systemd_version facts
Title: Message Title Julien Pivotto commented on FACT-852 Re: Add support for systemd and systemd_version facts I do think that three facts would be good: systemd_running (systemctl is-system-running) sytemd version (string) systemd flags (structured fact/list: +PAM -AUDIT -SELINUX -IMA -APPARMOR -SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD -IDN ) (systemctl --version) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Julien Pivotto commented on PUP-4516 Re: Agent does not stop with Ctrl-C https://github.com/puppetlabs/puppet/pull/4386 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title
Julien Pivotto commented on PUP-4516
Re: Agent does not stop with Ctrl-C
Josh Cooper
I would like to see the Signal in the message:
"Caught # {signal}
, exiting..."
Instead of "Exiting".
What do you think?
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5396) Puppet-agent package should display correct license information and URL
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5396
Puppet-agent package should display correct license information and URL
Change By:
Julien Pivotto
Puppt-agent package does not display valid license information and URL :{code:java}Name: puppet-agent Relocations: (not relocatable)Version : 1.2.4 Vendor: Puppet LabsRelease : 1.el7 Build Date: Fri 11 Sep 2015 02:53:46 AM CESTInstall Date: (not installed) Build Host: w54lt87eco67kfs.delivery.puppetlabs.netGroup : System Environment/Base Source RPM: puppet-agent-1.2.4-1.el7.src.rpmSize: 86182123 License: See componentsSignature : RSA/SHA1, Mon 21 Sep 2015 04:00:47 PM CEST, Key ID 7c5b6b1e14e3f551URL : https://www.puppetlabs.comSummary : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Description :The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Contains the following components:augeas 1.4.0curl 7.43.0dmidecode 2.12facter 3.1.0hiera 3.0.3marionette-collective 2.8.5openssl 1.0.2dpuppet 4.2.2ruby 2.1.6ruby-augeas 0.5.0ruby-selinux 2.0.94ruby-shadow 2.3.3ruby-stomp 1.3.3rubygem-deep-merge 1.0.1rubygem-hocon 0.9.3rubygem-net-ssh 2.1.4virt-what 1.1.4{code}See "License: See components".My proposal is to include license and information in the description, and to use CSV values to separate name, version , url and license. The licenses should ideally be identified by their SPDX short identifier http://spdx.org/licenses/{code}puppet,4.2.2,Apache-2.0,http://puppetlabs.comaugeas,1.4.0,LGPL-2.1,http://augeas.net{code}This proposal would make it easier for people who re-distribute the AIO package.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5396) Puppet-agent package should display correct license information and URL
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5396
Puppet-agent package should display correct license information and URL
Change By:
Julien Pivotto
Puppt-agent package does not display valid license information:{code:java}Name: puppet-agent Relocations: (not relocatable)Version : 1.2.4 Vendor: Puppet LabsRelease : 1.el7 Build Date: Fri 11 Sep 2015 02:53:46 AM CESTInstall Date: (not installed) Build Host: w54lt87eco67kfs.delivery.puppetlabs.netGroup : System Environment/Base Source RPM: puppet-agent-1.2.4-1.el7.src.rpmSize: 86182123 License: See componentsSignature : RSA/SHA1, Mon 21 Sep 2015 04:00:47 PM CEST, Key ID 7c5b6b1e14e3f551URL : https://www.puppetlabs.comSummary : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Description :The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Contains the following components:augeas 1.4.0curl 7.43.0dmidecode 2.12facter 3.1.0hiera 3.0.3marionette-collective 2.8.5openssl 1.0.2dpuppet 4.2.2ruby 2.1.6ruby-augeas 0.5.0ruby-selinux 2.0.94ruby-shadow 2.3.3ruby-stomp 1.3.3rubygem-deep-merge 1.0.1rubygem-hocon 0.9.3rubygem-net-ssh 2.1.4virt-what 1.1.4{code}See "License: See components".My proposal is to include license information in the description, and to use CSV values to separate name, version and license. The licenses should ideally be identified by their SPDX short identifier http://spdx.org/licenses/{code}puppet,4.2.2,Apache-2.0 ,http://puppetlabs.com augeas,1.4.0,LGPL-2.1,http://augeas.net {code}This proposal would make it easier for people who re-distribute the AIO package.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5396) Puppet-agent package should display correct license information and URL
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5396 Puppet-agent package should display correct license information and URL Change By: Julien Pivotto Summary: Puppet-agent package should display correct license information and URL Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5396) Puppet-agent package should display correct license information
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5396 Puppet-agent package should display correct license information Change By: Julien Pivotto Summary: Puppet-agent package should display correct licence license information Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5396) Puppet-agent package should display correct licence information
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5396 Puppet-agent package should display correct licence information Change By: Julien Pivotto Component/s: RE Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5396) Puppet-agent package should display correct licence information
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5396 Puppet-agent package should display correct licence information Change By: Julien Pivotto Labels: legal package Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5396) Puppet-agent package should display correct licence information
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5396
Puppet-agent package should display correct licence information
Change By:
Julien Pivotto
Puppt-agent package does not display valid license information:{code:java}Name: puppet-agent Relocations: (not relocatable)Version : 1.2.4 Vendor: Puppet LabsRelease : 1.el7 Build Date: Fri 11 Sep 2015 02:53:46 AM CESTInstall Date: (not installed) Build Host: w54lt87eco67kfs.delivery.puppetlabs.netGroup : System Environment/Base Source RPM: puppet-agent-1.2.4-1.el7.src.rpmSize: 86182123 License: See componentsSignature : RSA/SHA1, Mon 21 Sep 2015 04:00:47 PM CEST, Key ID 7c5b6b1e14e3f551URL : https://www.puppetlabs.comSummary : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Description :The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Contains the following components:augeas 1.4.0curl 7.43.0dmidecode 2.12facter 3.1.0hiera 3.0.3marionette-collective 2.8.5openssl 1.0.2dpuppet 4.2.2ruby 2.1.6ruby-augeas 0.5.0ruby-selinux 2.0.94ruby-shadow 2.3.3ruby-stomp 1.3.3rubygem-deep-merge 1.0.1rubygem-hocon 0.9.3rubygem-net-ssh 2.1.4virt-what 1.1.4{code}See "License: See components".My proposal is to include license information in the description, and to use CSV values to separate name, version and license. The licenses should ideally be identified by their SPDX short identifier http://spdx.org/licenses/{code}puppet,4.2.2,Apache-2.0{code} This proposal would make it easier for people who re-distribute the AIO package.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5396) Puppet-agent package should display correct licence information
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5396
Puppet-agent package should display correct licence information
Change By:
Julien Pivotto
Puppt-agent package does not display valid license information:{code:java}Name: puppet-agent Relocations: (not relocatable)Version : 1.2.4 Vendor: Puppet LabsRelease : 1.el7 Build Date: Fri 11 Sep 2015 02:53:46 AM CESTInstall Date: (not installed) Build Host: w54lt87eco67kfs.delivery.puppetlabs.netGroup : System Environment/Base Source RPM: puppet-agent-1.2.4-1.el7.src.rpmSize: 86182123 License: See componentsSignature : RSA/SHA1, Mon 21 Sep 2015 04:00:47 PM CEST, Key ID 7c5b6b1e14e3f551URL : https://www.puppetlabs.comSummary : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Description :The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Contains the following components:augeas 1.4.0curl 7.43.0dmidecode 2.12facter 3.1.0hiera 3.0.3marionette-collective 2.8.5openssl 1.0.2dpuppet 4.2.2ruby 2.1.6ruby-augeas 0.5.0ruby-selinux 2.0.94ruby-shadow 2.3.3ruby-stomp 1.3.3rubygem-deep-merge 1.0.1rubygem-hocon 0.9.3rubygem-net-ssh 2.1.4virt-what 1.1.4{code}See "License: See components".My proposal is to include license information in the description, and to use CSV values to separate name, version and license. The licenses should ideally be identified by their SPDX short identifier http://spdx.org/licenses/ {code}puppet,4.2.2,Apache-2.0{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5396) Puppet-agent package should display correct licence information
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5396
Puppet-agent package should display correct licence information
Change By:
Julien Pivotto
Puppt-agent package does not display valid license information:{code:java}Name: puppet-agent Relocations: (not relocatable)Version : 1.2.4 Vendor: Puppet LabsRelease : 1.el7 Build Date: Fri 11 Sep 2015 02:53:46 AM CESTInstall Date: (not installed) Build Host: w54lt87eco67kfs.delivery.puppetlabs.netGroup : System Environment/Base Source RPM: puppet-agent-1.2.4-1.el7.src.rpmSize: 86182123 License: See componentsSignature : RSA/SHA1, Mon 21 Sep 2015 04:00:47 PM CEST, Key ID 7c5b6b1e14e3f551URL : https://www.puppetlabs.comSummary : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Description :The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.Contains the following components:augeas 1.4.0curl 7.43.0dmidecode 2.12facter 3.1.0hiera 3.0.3marionette-collective 2.8.5openssl 1.0.2dpuppet 4.2.2ruby 2.1.6ruby-augeas 0.5.0ruby-selinux 2.0.94ruby-shadow 2.3.3ruby-stomp 1.3.3rubygem-deep-merge 1.0.1rubygem-hocon 0.9.3rubygem-net-ssh 2.1.4virt-what 1.1.4{code}See "License: See components".My proposal is to include license information in the description, and to use CSV values to separate name, version and license.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5396) Puppet-agent package should display correct licence information
Title: Message Title Julien Pivotto created an issue Puppet / PUP-5396 Puppet-agent package should display correct licence information Issue Type: Improvement Affects Versions: puppet-agent 1.2.5, puppet-agent 1.0.0 Assignee: Unassigned Components: AIO Created: 2015/10/20 3:49 AM Priority: Normal Reporter: Julien Pivotto Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Julien Pivotto commented on PUP-4516 Re: Agent does not stop with Ctrl-C Is there any plans to fix this? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Julien Pivotto commented on PUP-4516 Re: Agent does not stop with Ctrl-C No it is not an intentional change https://twitter.com/hel/status/640189459309441024 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5223) Support splat of Array as key of a Struct
Title: Message Title Julien Pivotto commented on PUP-5223 Re: Support splat of Array as key of a Struct PS : Hash[Variant[String, Optional, NotUndef], Type] comes from the Puppet doc Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5223) Support splat of Array as key of a Struct
Title: Message Title Julien Pivotto commented on PUP-5223 Re: Support splat of Array as key of a Struct Yes but the enum would not ensure that all the keys are defines Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5223) Support splat of Array as key of a Struct
Title: Message Title Julien Pivotto commented on PUP-5223 Re: Support splat of Array as key of a Struct Here is my usecase: https://gist.github.com/roidelapluie/523cccaae96b37fdf210 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5223) Support for Array as key of a Struct
Title: Message Title
Julien Pivotto commented on PUP-5223
Re: Support for Array as key of a Struct
Maybe it would be greats to be able to use splat there:
class test (
Array[Struct[{
'id' => String,
*['foo', 'barfoo', 'foobar'] => Struct[{
'status' => String,
'version' => String,
}],
}]] $foo,
){}
Question: Should the splat work there? In other words: is this a bug?
Jira (PUP-5223) Support for Array as key of a Struct
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5223
Support for Array as key of a Struct
Change By:
Julien Pivotto
Summary:
Support for arrays Array as keys key of a struct Struct
It would be nice if Struct Hash parameter would accept {code:puppet} Hash[Variant[String, Optional, NotUndef, Array[String, Optional, NotUndef]], Type] {code} instead of {code:puppet} Hash[Variant[String, Optional, NotUndef], Type] {code} That would allow struct to match the following:{code:puppet}class test ( Array[Struct[{'id' => String,['foo', 'barfoo', 'foobar'] => Struct[{ 'status' => String, 'version' => String,}], }]] $foo,){}{code}Currently we have to write that like this:{code:puppet}class test ( Array[Struct[{'id' => String,'foobar' => Struct[{ 'status' => String, 'version' => String,}],'barfoo' => Struct[{ 'status' => String, 'version' => String,}],'foo' => Struct[{ 'status' => String, 'version' => String,}], }]] $foo,){}{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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
