Jira (PUP-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title R.I.Pienaar commented on PUP-6472 Re: Puppet Lookup does only went through the module hieradata once indeed, doubt this ever worked for module data too, you're right 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-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title Thomas Hallgren commented on PUP-6472 Re: Puppet Lookup does only went through the module hieradata once R.I.Pienaar, I don't think this has ever worked when using a module data provider. I don't think making this kind of configs work will be very helpful (for reasons that I mentioned above). Further more, allowing local variables to redefine the actual configuration of the data provider will likely force a major rewrite and a far more inefficient implementation. 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-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title CJ Toolseram commented on PUP-6472 Re: Puppet Lookup does only went through the module hieradata once R.I.Pienaar the issue here is not about the global search, what i meant here was the local search, how do you confine the search locally? 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-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title R.I.Pienaar commented on PUP-6472 Re: Puppet Lookup does only went through the module hieradata once Best Practices say many supported things should not be done - that does not mean we should just not support them or fix bugs in them? I think this case used to work - certainly local vars used to. Yes a pain to debug but if that's not going to be supported it should go through deprecation cycle. 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-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title
Thomas Hallgren commented on PUP-6472
Re: Puppet Lookup does only went through the module hieradata once
The hiera configuration file uses %{title}/common in the hierarchy. That doesn't seem right to me. AFAIK, genericly speaking, there's no guarantee that a title is present when a lookup is made. There's also a fair chance of scenarios where the lookup data actually defines the title which would create a hen and egg problem.
Here's a quote from Using Hiera with Puppet/Best Practices:
Do not use local Puppet variables in Hiera’s hierarchy or data sources. Only use facts and ENC-set top-scope variables.
Using local variables can make your hierarchy incredibly difficult to debug.
So I would like to either close this as a "Won't fix" or change it so that it is about warn or error (depending on --strict option) when bad variables are used in a Hiera config. I'm not certain on what approach to use to detect that though.
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-6469) Pluralization not handled properly in `puppet apply --noop` message
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6469 Pluralization not handled properly in `puppet apply --noop` message Change By: Henrik Lindberg Priority: Normal Minor 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 (PDOC-77) Create an easy way to modify the rake task to include/exclude certain files/folders.
Title: Message Title Henrik Lindberg commented on PDOC-77 Re: Create an easy way to modify the rake task to include/exclude certain files/folders. It is in "Ready for CI" which is past "Ready for Merge". Someone needs to look at the acceptance test results to move it to the next state: "Ready for Test". 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-6470) EPP - Syntax error raised in wrong location after attempting .empty? in template
Title: Message Title
Henrik Lindberg commented on PUP-6470
Re: EPP - Syntax error raised in wrong location after attempting .empty? in template
the ? is an operator in the puppet language so expr ? }} is valid. It becomes invalid at the {{[ just as it reported. The grammar / validator cannot know what was intended. In this case there is no way to improve on the location reporting.
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-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6472 Puppet Lookup does only went through the module hieradata once Thomas Hallgren Can you take a look at this? Change By: Henrik Lindberg Sprint: Language Triage Scrum Team: Language 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-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-6472 Puppet Lookup does only went through the module hieradata once Change By: Henrik Lindberg Key: HI PUP - 521 6472 Project: Hiera Puppet 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-6471) Add toggle to disable symlinks in the file server
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6471 Add toggle to disable symlinks in the file server Change By: Henrik Lindberg Scrum Team: Puppet Server 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-6397) File autorequire in Mount causes dependency loops
Title: Message Title Mihkel Ader updated an issue Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: Mihkel Ader Priority: Normal Major 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-6397) File autorequire in Mount causes dependency loops
Title: Message Title
Mihkel Ader commented on PUP-6397
Re: File autorequire in Mount causes dependency loops
An even simpler example that fails with dependency loop in Puppet 4.5.x but works fine in 4.4.x. Seems that the mount autobefore matches totally irrelevant "child" file resources?
file { '/tmp/home/test/': ensure => 'directory', }
-> file { '/tmp/home/test/test': ensure => 'file', }
-> mount { "/home": }
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.
