Jira (PUP-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Zachary Smith commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Also to the 3.x variant ( the glue code as it were ) is called via puppet not ruby. Its littered throughout manifests all over the code. So this was an attempt to make the 3.x function stay the same and have the condtional logic above send the args to the correct 4.x function int he case of 4 and the legacy_ 3.x function int he case of 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Zachary Smith commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes in my case, Puppet 3.x is working but Puppet 4.x is not. Though its always hard to say with SERVER-94 handing over my head 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Henrik Lindberg assigned an issue to Zachary Smith Puppet / PUP-5930 If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Change By: Henrik Lindberg Assignee: Henrik Lindberg Zachary Smith 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Henrik Lindberg commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes A stack trace between the recursive spots would be great. My main question is - what makes the old (3.x) variant be called in the first place? Are they on puppet 3.x? Then if not running with future parser, then naturally there is a recursion since call_function always works and it would indeed call back recursively. If future parser was on, it is possible to call into the 3.x version by invoking the function via the scope by calling Scope.function_ get_ldap_group, but then, when call_function is invoked, it would find and call the 4.x version. Hence - I suspect that sometimes they are running without future parser. 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-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long I posted a pull request that addresses this issue upstream. I'll let it sit there for a few days for others to comment before I merge it. Michael Stahnke It would be good to get some guidance on when I'd need to make the next upstream release so that that can be included in newer puppet-agent builds (i.e., what's the next puppet -agent release we could get this into, and by when does the upstream release need to happen for that) 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Zachary Smith assigned an issue to Henrik Lindberg Puppet / PUP-5930 If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Change By: Zachary Smith Assignee: Zachary Smith Henrik Lindberg 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title
Zachary Smith commented on PUP-5930
Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
For even more context I was trying to get around and issue that ruby 1.8.7 could not load the new function code , so rewriting this new function via the new API effectively causes older versions of puppet ( and thus ruby) from not ever evaluating the file so you can put stuff like named arguments in it.
I thought why not make them the same name as I assume the 3.x function wouldn't mind sharing a name. The OOM thats happening makes me thing this is isnt quite as clear cut as that. Thus my original assumption was that somehow the original 3.x function is getting called, and then the call_function('get_ldap_group', args) is not calling the 4.x but instead recursively calling the 3.x forever until it OOMs.
I will have to mock this up, any data from puppetserver you explicit?
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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Zachary Smith commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes in the above example there are two get_ldap_group function one 3.x and one 4.x (obviously in different files i.e. parser/fuctions and ./functions ) The 3.x is there mostly to allow for old code to keep working and send older puppet 3/ ruby 1.8.7 masters the args via the original code which in the example above is called legacy_get_ldap_group. 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Zachary Smith commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes I am glad thats the expected behavior as thats what I was expecting. Not sure what you meant by emdeding 3.x inside 4.x the two code blocks are different files. This seems pretty repeatable as I have had it a couple times now. I will throw it in vagrant and try and build something from the customer examples that caused 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 (PUP-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long It's a buffer overflow in the code that generates the error message caused by having save fail. I opened https://github.com/hercules-team/augeas/issues/349 upstream to address that (and have a fix almost ready) 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-5878) acceptance: agent can reconnect after master failure
Title: Message Title Eric Thompson commented on PUP-5878 Re: acceptance: agent can reconnect after master failure this thing is much more difficult to accomplish than at first glance. We should revisit with a full plan to test the http connections under various scenarios of duress. Just this one case, you'd think could be accomplished via killing the master with kill -9 between connection initiation and before a catalog is sent. but this seems to send a RST to the agent. and it can reconnect later without any issues, even before the fix in the upstream ticket. I have not been able to reproduce the behavior in the upstream ticket which appears to require something like powerloss during a compilation. 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-5569) acceptance: to ensure Resource Collectors can use resource references in search expressions
Title: Message Title Eric Thompson assigned an issue to Henrik Lindberg Puppet / PUP-5569 acceptance: to ensure Resource Collectors can use resource references in search expressions Change By: Eric Thompson Assignee: Henrik Lindberg 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-5936) a given undef should set undef and not require a default expression of = undef
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5936 a given undef should set undef and not require a default _expression_ of = undef Change By: Henrik Lindberg Story Points: 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-5936) a given undef should set undef and not require a default expression of = undef
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-5936
a given undef should set undef and not require a default _expression_ of = undef
Issue Type:
Improvement
Assignee:
Thomas Hallgren
Created:
2016/02/19 4:39 PM
Fix Versions:
PUP 4.4.0, PUP 4.3.3
Priority:
Normal
Reporter:
Henrik Lindberg
In PUP-5925 we made it possible to give an undef value in a data binding and allowing that to mean that undef is assigned to a class parameter if that class parameter does not have a default value _expression_ (the default _expression_ wins using the rule "a undef given value means 'use the default").
In this ticket we should do the same for the resource _expression_. Such that if user has the following:
define foo(Optional[Integer] $x) { }
foo { 'example': x => undef }
Jira (PUP-5935) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Henrik Lindberg commented on PUP-5935 Re: Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Erik Hansen for an excellent bug report and a reproducible case. 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-5935) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5935 Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Change By: Henrik Lindberg Priority: Normal Major 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-5935) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5935 Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Change By: Henrik Lindberg Fix Version/s: PUP 4.3.3 Fix Version/s: PUP 4.4.0 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-5935) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Henrik Lindberg commented on PUP-5935 Re: Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Thomas Hallgren does this sound familiar? Something that is already fixed in Puppet 4.4.0 ? 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-5935) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Henrik Lindberg commented on PUP-5935 Re: Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Note that 'data in modules' is a puppet and not a hiera feature (not easy to know). I moved the ticket to the PUP project. 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-5935) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5935 Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Change By: Henrik Lindberg Sprint: Client Triage Scrum Team: Language 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-5935) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-5935 Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Change By: Henrik Lindberg Key: HI PUP - 498 5935 Project: Hiera Puppet 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-5873) Ensure generated file resources in static catalog are contained
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5873 Ensure generated file resources in static catalog are contained Change By: Josh Cooper Fix Version/s: PUP 4.4.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-5114) Retrieve content using content_uri
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5114 Retrieve content using content_uri Change By: Michael Smith Assignee: Michael Smith 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 (HI-498) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title
Erik Hansen updated an issue
Hiera / HI-498
Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Change By:
Erik Hansen
Observed in PE 2015.3.1I've attached an archive that contains two modules, test1 and test2. These two modules each have their own set of heira parameters based on the version 4 standards. Each module contains a single defined type (test1::foo and test2::foo2) and each of these defined types references it's own module's hiera data. Where I start to see problems is when test2::foo2 is called from within the test1::foo defined type. In that instance it will no longer have access to it's hiera parameters from the test2 module. With the modules unpacked and installed do: {code}[root@pe-201531-master modules]# puppet apply -e 'test1::foo {"TEST":}'Error: Evaluation Error: Error while evaluating a Resource Statement, Function lookup() did not find a value for the name 'test2::foo::message' at /etc/puppetlabs/code/environments/production/modules/test1/manifests/foo.pp:5 on node pe-201531-master.puppetdebug.vlan{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
Jira (HI-498) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title
Erik Hansen updated an issue
Hiera / HI-498
Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Change By:
Erik Hansen
Observed in PE 2015.3.1I've attached an archive that contains two modules, test1 and test2. These two modules each have their own set of heira parameters based on the version 4 standards. Each module contains a single defined type (test1::foo and test2::foo2) and each of these defined types references it's own module's hiera data. Where I start to see problems is when test2::foo2 is called from within the test1::foo defined type. In that instance it will no longer have access to it's hiera parameters from the test2 module.{ quote code }[root@pe-201531-master modules]# puppet apply -e 'test1::foo {"TEST":}' Error: Evaluation Error: Error while evaluating a Resource Statement, Function lookup() did not find a value for the name 'test2::foo::message' at /etc/puppetlabs/code/environments/production/modules/test1/manifests/foo.pp:5 on node pe-201531-master.puppetdebug.vlan{ quote 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
Jira (HI-498) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title
Erik Hansen updated an issue
Hiera / HI-498
Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Change By:
Erik Hansen
Observed in PE 2015.3.1I've attached an archive that contains two modules, test1 and test2. These two modules each have their own set of heira parameters based on the version 4 standards. Each module contains a single defined type (test1::foo and test2::foo2) and each of these defined types references it's own module's hiera data. Where I start to see problems is when test2::foo2 is called from within the test1::foo defined type. In that instance it will no longer have access to it's hiera parameters from the test2 module.{quote}[root@pe-201531-master modules]# puppet apply -e 'test1::foo {"TEST":}' Error: Evaluation Error: Error while evaluating a Resource Statement, Function lookup() did not find a value for the name 'test2::foo::message' at /etc/puppetlabs/code/environments/production/modules/test1/manifests/foo.pp:5 on node pe-201531-master.puppetdebug.vlan{quote}
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
Jira (HI-498) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Erik Hansen updated an issue Hiera / HI-498 Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Change By: Erik Hansen CS Priority: Needs Priority 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 (HI-498) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title
Erik Hansen updated an issue
Hiera / HI-498
Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Change By:
Erik Hansen
Observed in PE 2015.3.1I've attached an archive that contains two modules, test1 and test2. These two modules each have their own set of heira parameters based on the version 4 standards. Each module contains a single defined type (test1::foo and test2::foo2) and each of these defined types references it's own module's hiera data. Where I start to see problems is when test2::foo2 is called from within the test1::foo defined type. In that instance it will no longer have access to it's hiera parameters from the test2 module. {quote} [root@pe-201531-master modules]# puppet apply -e 'test1::foo {"TEST":}'Error: Evaluation Error: Error while evaluating a Resource Statement, Function lookup() did not find a value for the name 'test2::foo::message' at /etc/puppetlabs/code/environments/production/modules/test1/manifests/foo.pp:5 on node pe-201531-master.puppetdebug.vlan {quote}
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
Jira (HI-498) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title Erik Hansen updated an issue Hiera / HI-498 Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module Change By: Erik Hansen Attachment: testmodules.tar.gz 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 (HI-498) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title
Erik Hansen updated an issue
Hiera / HI-498
Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Change By:
Erik Hansen
Observed in PE 2015.3.1I've attached an archive that contains two modules, test1 and test2. These two modules each have their own set of heira parameters based on the version 4 standards. Each module contains a single defined type (test1::foo and test2::foo2) and each of these defined types references it's own module's hiera data. Where I start to see problems is when test2::foo2 is called from within the test1::foo defined type. In that instance it will no longer have access to it's hiera parameters from the test2 module. {{ [root@pe-201531-master modules]# puppet apply -e 'test1::foo {"TEST":}'Error: Evaluation Error: Error while evaluating a Resource Statement, Function lookup() did not find a value for the name 'test2::foo::message' at /etc/puppetlabs/code/environments/production/modules/test1/manifests/foo.pp:5 on node pe-201531-master.puppetdebug.vlan }}
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
Jira (HI-498) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Title: Message Title
Erik Hansen created an issue
Hiera / HI-498
Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/02/19 3:39 PM
Priority:
Normal
Reporter:
Erik Hansen
Observed in PE 2015.3.1
I've attached an archive that contains two modules, test1 and test2. These two modules each have their own set of heira parameters based on the version 4 standards.
Each module contains a single defined type (test1::foo and test2::foo2) and each of these defined types references it's own module's hiera data.
Where I start to see problems is when test2::foo2 is called from within the test1::foo defined type. In that instance it will no longer have access to it's hiera parameters from the test2 module.
{{[root@pe-201531-master modules]# puppet apply -e 'test1::foo {"TEST":}
' Error: Evaluation Error: Error while evaluating a Resource Statement, Function lookup() did not find a value for the name 'test2::foo::message' at /etc/puppetlabs/code/environments/production/modules/test1/manifests/foo.pp:5 on node pe-201531-master.puppetdebug.vlan}}
Add Comment
Jira (PUP-5933) Don't set pluginsync in puppet.conf on Windows
Title: Message Title Rob Reynolds commented on PUP-5933 Re: Don't set pluginsync in puppet.conf on Windows Adding the same note here: That this will not remove it from existing installations of Puppet. The value in the conf file will still be there. So you may need to do something additional to remove that (which maybe is what the deprecation warning is for). 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Reid Vandewiele commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run The facts at the time the report was submitted seems kind of meaningless. Those fact values weren't used for anything and so don't correspond to anything else, including the report. What you're really asking for is very current facts. I think that's what we should aim for, not piggybacking the facts on the last known thing the agent did. Yes, I think that's accurate. The suggestion of report submission time was born out of an imagined implementation, and still might make a good first "all facts must be up to date when this event occurs no matter what" milestone. That said, if there were some magical way of just always having up-to-date facts instead, that would totally solve the problem statement. 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-5933) Don't set pluginsync in puppet.conf on Windows
Title: Message Title Rob Reynolds commented on PUP-5933 Re: Don't set pluginsync in puppet.conf on Windows Merged into master at https://github.com/puppetlabs/puppet_for_the_win/commit/d58e6a7346fb1ab249323047fb15ac1016050ce9. 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 Henrik Lindberg commented on PDOC-43 Re: Allow more advanced formatting in parameters descriptions Ok, were there more formatting than bold? I would like to keep the ticket and modify it to describe the features that are missing. We may adopt your PR even and continue the work. Sorry for the long silence. 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Kylo Ginsberg commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Hmm, this may warrant a chat to get right. If anything I've thought about decoupling fact submission from agent runs entirely, and ideally making them submitted at different rates depending on their volaitility. In part that idea is inspired by concerns like the one you raise here: The longer the time window during which node B's PuppetDB facts are out sync with the node's real fact values, the longer it takes for the infrastructure as a whole to converge on a correct, consistent configuration. In any event, re the solution requested: Puppet should submit updated fact values at the end of each run along with the report. The facts at the time the report was submitted seems kind of meaningless. Those fact values weren't used for anything and so don't correspond to anything else, including the report. What you're really asking for is very current facts. I think that's what we should aim for, not piggybacking the facts on the last known thing the agent did. 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 (PDOC-43) Allow more advanced formatting in parameters descriptions
Title: Message Title Henrik Lindberg commented on PDOC-43 Re: Allow more advanced formatting in parameters descriptions Julien Pivotto Did you give up on this because you ran into issues? Not sure what exactly the feature was supposed to do, so hard to say how valuable your idea is. We are going to come back and do work on Strings but we have been busy with other things for a while. 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 (PDB-2454) max-command-size default value is too small
Title: Message Title Reid Vandewiele created an issue PuppetDB / PDB-2454 max-command-size default value is too small Issue Type: Bug Assignee: Unassigned Created: 2016/02/19 2:58 PM Priority: Normal Reporter: Reid Vandewiele Using a normal Puppet codebase on a small VM, it is very easy for catalogs to exceed the default max-command-size for PuppetDB. The following logs are an example run in the standard TSE environment, trying to compile a catalog for the Puppet Enterprise master. terminal [root@master ~]# puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts
Jira (PUP-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title John Duarte updated an issue Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: John Duarte Comment: [~john.duarte] what you pasted has typos. Does it work if you use two colons as separator? The sample you showed for master is correct. 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title
John Duarte updated an issue
Puppet / PUP-5761
when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Change By:
John Duarte
Comment:
Fails using {{puppet-agent#stable}} at SHA {{dc4425ef249efd7bba2379ef4137994e516737c5}} containing {{puppet}} at SHA {{411f62e4119ac79a9530e56791c8533f160d0dfa}};A {{puppet apply}} is able to successfully perform the lookup function. However, using {{puppet lookup}} command fails find the key.Output of interaction{code}root@ffjmcu2dff110lj:~# puppet apply -e 'include hello'Warning: Module data for module 'hello' must use keys qualified with the name of the moduleNotice: Scope(Class[Hello]): module-hello-ruby-function provided dataNotice: Compiled catalog for ffjmcu2dff110lj.delivery.puppetlabs.net in environment production in 0.17 secondsNotice: Applied catalog in 0.02 secondsroot@ffjmcu2dff110lj:~# puppet lookup hello:module_keyroot@ffjmcu2dff110lj:~# echo $?1root@ffjmcu2dff110lj:~# puppet lookup hello:module_key --explainMerge strategy first Data Binding "hiera"No such key: "hello:module_key" Data Provider "EnvironmentDataProvider"No such key: "hello:module_key"{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
Jira (PUP-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5934 Updated fact values should be submitted after each Puppet run Ping Kylo Ginsberg Change By: Henrik Lindberg Scrum Team: Client Platform 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Henrik Lindberg Status: Ready for Engineering Test Assignee: John Duarte qa 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg commented on PUP-5761 Re: when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing John Duarte what you pasted has typos. Does it work if you use two colons as separator? 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg assigned an issue to John Duarte Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Henrik Lindberg Assignee: Henrik Lindberg John Duarte 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title John Duarte assigned an issue to Henrik Lindberg Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: John Duarte Assignee: John Duarte Henrik Lindberg 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Henrik Lindberg assigned an issue to Zachary Smith Puppet / PUP-5930 If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Change By: Henrik Lindberg Assignee: Zachary Smith 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Henrik Lindberg commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Do you have 3.x calls to the same function in your ruby code somewhere? If not, it should be impossible for the 3.x function to be calle In your example it looks like you included a 3.x function definition inside of a 4.x function. ?!?? WAT. I hope that is not the case. Can you show the 4.x version and also how you called this to make it error. We have several shadowed 3.x functions that just throws an exception if they are invoked (when they were replaced with a 4.x version). In 3.x with future parser we use this so that when parser=future is in effect you see the real 4.x functions, and if you call functions that are only available when parser=future is in effect you get an error saying so. 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title John Duarte commented on PUP-5761 Re: when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Fails using puppet-agent#stable at SHA dc4425ef249efd7bba2379ef4137994e516737c5 containing puppet at SHA 411f62e4119ac79a9530e56791c8533f160d0dfa; A puppet apply is able to successfully perform the lookup function. However, using puppet lookup command fails find the key. Output of interaction root@ffjmcu2dff110lj:~# puppet apply -e 'include hello' Warning: Module data for module 'hello' must use keys qualified with the name of the module Notice: Scope(Class[Hello]): module-hello-ruby-function provided data Notice: Compiled catalog for ffjmcu2dff110lj.delivery.puppetlabs.net in environment production in 0.17 seconds Notice: Applied catalog in 0.02 seconds root@ffjmcu2dff110lj:~# puppet lookup hello:module_key root@ffjmcu2dff110lj:~# echo $? 1 root@ffjmcu2dff110lj:~# puppet lookup hello:module_key
Jira (PUP-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Henrik Lindberg commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes The expected behavior is that the 4.x version of the function wins. 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5930 If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Change By: Henrik Lindberg Sprint: Language Triage Scrum Team: Language 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Reid Vandewiele created an issue Puppet / PUP-5934 Updated fact values should be submitted after each Puppet run Issue Type: New Feature Assignee: Unassigned Created: 2016/02/19 2:31 PM Priority: Normal Reporter: Reid Vandewiele Today it is the case that facts are generated prior to a Puppet run, then Puppet makes changes to the system. Because changes are made, it may be the case that the true value of a fact for a system will have changed after the run, but it will not be updated in PuppetDB until the run interval elapses (typically 30 minutes) and the next run begins. It is becoming common for PuppetDB queries to be used to select nodes based on fact values, for grouping and reporting. In addition, modules like Erik Dalén's puppetdbquery allow the master to build catalogs for node A based on facts about node B. The longer the time window during which node B's PuppetDB facts are out sync with the node's real fact values, the longer it takes for the infrastructure as a whole to converge on a correct, consistent configuration. Additionally, the intuitive mental model of reading Puppet reports and fact lists in the console is "Puppet submitted a report at time X, therefore I know that the facts shown are valid as of time X". However, this is not true today as described above. Feature Request In addition to submitting facts at the beginning of each run, Puppet should submit updated fact values at the end of each run along with the report.
Jira (PUP-5931) puppet config print does not work if you are not the master
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5931 puppet config print does not work if you are not the master Ping Kylo Ginsberg Change By: Henrik Lindberg Scrum Team: Client Platform 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title John Duarte commented on PUP-5761 Re: when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Validated via puppet-agent#master at SHA 9d6ed6fb9ff96306d4737c9f148d48a4e362fbcf containing puppet at SHA 7463c7e0c6333e85b3f20ede2143b600e798c90e A warning is issued for the unqualified key, but the lookup succeeds. Transaction of interaction based on hello module defined in the description of this ticket. root@nwb0hmyyohgh0yb:/etc/puppetlabs/code/environments/production/modules# puppet lookup hello::module_key Warning: Module data for module 'hello' must use keys qualified with the name of the module --- module-hello-ruby-function provided data ... root@nwb0hmyyohgh0yb:/etc/puppetlabs/code/environments/production/modules# puppet lookup hello::module_key --explain Warning: Module data for module 'hello' must use keys qualified with the name of the module Merge strategy first Data Binding "hiera"
Jira (PDB-2453) Remove Ubuntu 15.04 Vivid as a build target
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-2453 Remove Ubuntu 15.04 Vivid as a build target Issue Type: Task Assignee: Unassigned Created: 2016/02/19 2:25 PM Priority: Normal Reporter: Melissa Stone 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
Jira (PDB-2452) Remove Ubuntu 15.04 Vivid from testing
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-2452 Remove Ubuntu 15.04 Vivid from testing Issue Type: Task Assignee: Unassigned Created: 2016/02/19 2:25 PM Priority: Normal Reporter: Melissa Stone 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
Jira (PUP-5933) Don't set pluginsync in puppet.conf on Windows
Title: Message Title William Hopper created an issue Puppet / PUP-5933 Don't set pluginsync in puppet.conf on Windows Issue Type: Bug Assignee: Unassigned Created: 2016/02/19 2:17 PM Environment: Windows Fix Versions: PUP 4.4.0 Priority: Normal Reporter: William Hopper Currently, we set pluginsync=true in puppet.conf on Windows. This is a problem since we now log deprecation warnings when pluginsync is set via the CLI or config. Pluginsync still defaults to true, so there's no reason to set it in Puppet.conf. Add Comment
Jira (PDB-2449) Remove fedora 21 from testing
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-2449 Remove fedora 21 from testing Issue Type: Task Assignee: Unassigned Created: 2016/02/19 2:09 PM Priority: Normal Reporter: Melissa Stone 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
Jira (PUP-5928) Add pattern matching to Runtime Type
Title: Message Title Henrik Lindberg commented on PUP-5928 Re: Add pattern matching to Runtime Type I updated the description. Please edit it if something is missing/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 (PDB-2450) Remove Fedora 21 as a build target
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-2450 Remove Fedora 21 as a build target Issue Type: Task Assignee: Unassigned Created: 2016/02/19 2:09 PM Priority: Normal Reporter: Melissa Stone 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
Jira (PDB-2451) disable fedora 21 test cells
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-2451 disable fedora 21 test cells Issue Type: Task Assignee: Unassigned Created: 2016/02/19 2:09 PM Priority: Normal Reporter: Melissa Stone 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
Jira (PUP-5928) Add pattern matching to Runtime Type
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5928
Add pattern matching to Runtime Type
Change By:
Henrik Lindberg
Currently the {{Runtime}} type can describe only one class at the time. As we plan to use this to provide mappings from general models to an implementation (e.g. to bind AST related classes like Locator, or the AST itself) to puppet names in such a way that implementations in different languages can read/write a data stream where instances are identified by the puppet name), it is onerous having to individually define those mappings (AST =~ 100 classes).To support this, the {{Runtime}} type should provide regular _expression_ substitution support by stating a Regular _expression_ and a substitution . Currently it only accepts a single classname.{code:puppet}$in_my_package_t = Runtime[ruby, [ /MyPackage:: ( .* ) / , 'MyModule::\1' ] ] {code}can then be used to answer if an implementation instance is an instance of that runtime type.
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-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title Henrik Lindberg commented on PUP-5929 Re: Allow type alias to define a mapping between puppet names and runtime types Yes I agree. 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-4545) Too many restarts on interface changes for Fedora, RHEL, CentOS
Title: Message Title David Danzilio commented on PUP-4545 Re: Too many restarts on interface changes for Fedora, RHEL, CentOS Just submitted a PR to remove this: https://github.com/puppetlabs/puppet/pull/4688 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-5925) Optional data type and data binding with undef as default value
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5925 Optional data type and data binding with undef as default value Change By: Henrik Lindberg Release Notes Summary: A small but annoying problem in data binding has been fixed, where if you defined a data key for a parameter to be nil (i.e. undef) and did not have a default _expression_ for the parameter that also specified undef (or some other value) an error would be raised. Now, if nil/undef is bound as value in data, and there is no default _expression_, the value undef is assigned to the parameter instead of giving an error). Release Notes: Bug Fix 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: John Duarte Assignee: qa John Duarte 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-4818) PUP-121 (relative namespacing) was never fully resolved in 3.x future parser
Title: Message Title John Duarte commented on PUP-4818 Re: PUP-121 (relative namespacing) was never fully resolved in 3.x future parser Also validated via puppet-agent#stable at SHA dc4425ef249efd7bba2379ef4137994e516737c5 containing puppet at SHA 411f62e4119ac79a9530e56791c8533f160d0dfa puppet-agent#master at SHA 9d6ed6fb9ff96306d4737c9f148d48a4e362fbcf containing puppet at SHA 7463c7e0c6333e85b3f20ede2143b600e798c90e 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-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long That OVA works for me .. I can reproduce the issue with it. 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-5932) Error: Package: puppet-3.8.6-1.el7.noarch (puppetlabs-products) Requires: ruby(selinux)
Title: Message Title Vijesh created an issue Puppet / PUP-5932 Error: Package: puppet-3.8.6-1.el7.noarch (puppetlabs-products) Requires: ruby(selinux) Issue Type: Improvement Affects Versions: PUP 3.8.5 Assignee: Unassigned Components: Puppet Server Created: 2016/02/19 12:21 PM Priority: Normal Reporter: Vijesh Error: Package: puppet-3.8.6-1.el7.noarch (puppetlabs-products) Requires: ruby(selinux) Please include the dependencies in the package. OS: RHEL7 Add Comment
Jira (PUP-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long Geoff Williams it appears that the VM in question is not available from the download site anymore. When I download http://downloads.puppetlabs.com/training/puppet-2015.2.1-student-2.33.ova I actually have puppet-2015.3.1-student-3.2.ovf inside the OVA file 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-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long Just to be very clear: this is not simply a matter of augeas segfaulting with an invalid path. I haven't been able to reproduce that with either augeas-1.4.0 (shipped in puppetagent-1.2.2) or augeas-1.5.0 (latest release) by mimicking the commands that the Puppet provider issues. It's probably some other interaction between Puppet, ruby-augeas, and augeas itself; I am not saying there's no bug in augeas behind it, but it's certainly not as simple as "invalid paths in Augeas commands lead to segfaults" 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-5931) puppet config print does not work if you are not the master
Title: Message Title Zachary Smith created an issue Puppet / PUP-5931 puppet config print does not work if you are not the master Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Created: 2016/02/19 11:44 AM Priority: Normal Reporter: Zachary Smith One of our support engineers sent the following to a customer: curl --cert $(puppet config print hostcert) \ --key $(puppet config print hostprivkey) \ --cacert $(puppet config print cacert) \
Jira (PUP-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort assigned an issue to David Lutterkort Puppet / PUP-5479 segfault with augeas type when changes attribute is too long Change By: David Lutterkort Assignee: Kylo Ginsberg David Lutterkort 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-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Zachary Smith created an issue Puppet / PUP-5930 If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Components: Puppet Server Created: 2016/02/19 11:38 AM Priority: Normal Reporter: Zachary Smith I was playing around with the new function api and was curios if I could have an old and new function named the same thing. I wrote some code that looked like this: # 4.x Puppet::Functions.create_function(:get_ldap_group) do
Jira (PUP-5907) Define the PCore Serialization API and Features
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5907
Define the PCore Serialization API and Features
Change By:
Henrik Lindberg
The goal of the PCore serialization feature is to provide consistent serialization between two parties that may have completely different implementation. * The implementation objects being used to represent runtime values that are to be part of a serialization should be free from serialization concern. (e.g. we want to avoid having to have {{to_yaml}}, {{to_this}}, {{to_that}} as methods on runtime objects.* Everything that is part of a serialization muse be modeled by a PCore model. It is the PCore model that controls how the values of a runtime objects should be serialized.* The serialization APIs should be agnostic towards the resulting serialization "on the wire format"; e.g. if it is binary or textual, if it is optimized/tabulated or if it is human readable / understandable.* The API should allow 3d party serialization formats to be defined (i.e. this should be an open ended design). It does not have to specify how such formats are discovered, but the API itself should be open.* When two parties communicate indirectly e.g. via a persisted file, the file must contain an envelope that makes it possible to discover how it should be deserialized. When two parties communicate directly they can agree on a format up front.* The serialization should be agnostic towards the implementation used at either end of a transfer; no runtime implementation specific information should be embedded in the serialization (i.e. no instances of Ruby/C++/Java classes). A mapping via a PCore model is always required. For puppet type system built in data types (e.g. Integer), each side is expected to have a base implementation that deals with this mapping, either via a PCore type mapping and use of generic objects, or by binding it in that that languages runtime in a hard coded fashion.* each serialization must (either via envelope or protocol negotiation) establish the identifier of the PCore model to use for serialization. That model in turn needs to reference any auxiliary PCore models that it relies on. It is then up to each side to use a binding of the PCore references to something that works in the respective side's implementation. (e.g. In Ruby a Locator in an AST is a Puppet::Pops::Model::Locator, in C++ it may have a completely different class name).
Add Comment
Jira (PDB-2448) (maint) bump EZbake version
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2448 (maint) bump EZbake version Issue Type: Bug Assignee: Unassigned Created: 2016/02/19 10:21 AM Priority: Normal Reporter: gepetto-bot This will bump the EZBake version due to a recent release Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5914) data binding: a way to set the merge behaviour (like in the lookup() function) ?
Title: Message Title Francois Lafont commented on PUP-5914 Re: data binding: a way to set the merge behaviour (like in the lookup() function) ? Ok, so finally, for the lookup_options key itself, I don't see any difference between the merge you describe and the deep merge, unless I have missed something. Anyway, now I have lot of personal modules to rewrite to use this excellent data binding mechanism (which I have well understood now I think). Thx again. 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 (PDB-2448) (maint) bump EZbake version
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2448 (maint) bump EZbake version Change By: gepetto-bot Sprint: PuppetDB 2016-02-24 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 (PDB-2447) (maint) Bump EZbake version
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2447 (maint) Bump EZbake version Change By: gepetto-bot Sprint: PuppetDB 2016-02-24 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 (PDB-2447) (maint) Bump EZbake version
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2447 (maint) Bump EZbake version Issue Type: Bug Assignee: Unassigned Created: 2016/02/19 10:17 AM Priority: Normal Reporter: gepetto-bot This bumps the EZBake version due to a new release of EZBake Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5844) Add the Object type to the Puppet Type system
Title: Message Title Henrik Lindberg commented on PUP-5844 Re: Add the Object type to the Puppet Type system See PUP-5929 for the type aliases with patterns See PUP-5928 for pattern matching in Runtime type See PUP-5927 for default value on Optional type 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-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5929
Allow type alias to define a mapping between puppet names and runtime types
Change By:
Henrik Lindberg
When doing serialization between runtimes of different versions or implementation languages it is of value to be able to define the mapping between names in the puppet name space and the implementation that is performing the operation.This relates to PUP-5928 where it is possible to define a pattern so that each class in a package does not have to be stated and instead be matched with a pattern. The functionality in PUP-5928 is used here for further functionality.The type alias mechanism should be extended to give special meaning to a mapping of a {{Runtime}} type to a Puppet Type. The semantics of this is "this runtime type is a representation of this puppet type".As an example - this is what puppet uses internally:{code:puppet}type Runtime[ruby, Float] = Float{code}By making it possible to specify these mappings, there is nothing special or secret about any of the mappings. Serialization simply refers to a type model to know what the bindings are supposed to be in the implementation that serializes/deserializes.It is of great value to use the pattern in PUP--5928 to also specify the RHS:{code:puppet}type Runtime[ ' ruby ' , [ / MyPackage ^Puppet :: P Pops::Model:: ( .* \w+ ) Type $ / , 'PCore::AST::\1' ] ] = [ MyModule /^PCore :: MyPackage AST::(\w+)$/ , " 'Puppet::Pops::Model:: \1 " ' ]{code}(Or similar syntax). This would mean, all the classes in the Ruby MyPackage that has the pattern PType would be mapped to the corresponding puppet name e.g. MyPackage::PFooType is mapped to MyModule::MyPackage::Foo as a puppet name.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title Thomas Hallgren commented on PUP-5929 Re: Allow type alias to define a mapping between puppet names and runtime types I think both sides in the assignment need both a pattern and a substitution since the mapping is bidirectional. 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-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5929
Allow type alias to define a mapping between puppet names and runtime types
Change By:
Henrik Lindberg
When doing serialization between runtimes of different versions or implementation languages it is of value to be able to define the mapping between names in the puppet name space and the implementation that is performing the operation.This relates to PUP-5928 where it is possible to define a pattern so that each class in a package does not have to be stated and instead be matched with a pattern. The functionality in PUP-5928 is used here for further functionality.The type alias mechanism should be extended to give special meaning to a mapping of a {{Runtime}} type to a Puppet Type. The semantics of this is "this runtime type is a representation of this puppet type".As an example - this is what puppet uses internally:{code :puppet }type Runtime[ruby, Float] = Float{code}By making it possible to specify these mappings, there is nothing special or secret about any of the mappings. Serialization simply refers to a type model to know what the bindings are supposed to be in the implementation that serializes/deserializes.It is of great value to use the pattern in PUP--5928 to also specify the RHS:{code:puppet}type Runtime[ruby, /MyPackage::P(.*)Type/] = [MyModule::MyPackage, "\1"]{code}(Or similar syntax). This would mean, all the classes in the Ruby MyPackage that has the pattern PType would be mapped to the corresponding puppet name e.g. MyPackage::PFooType is mapped to MyModule::MyPackage::Foo as a puppet name.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5929
Allow type alias to define a mapping between puppet names and runtime types
Change By:
Henrik Lindberg
When doing serialization between runtimes of different versions or implementation languages it is of value to be able to define the mapping between names in the puppet name space and the implementation that is performing the operation.This relates to PUP-5928 where it is possible to define a pattern so that each class in a package does not have to be stated and instead be matched with a pattern. The functionality in PUP-5928 is used here for further functionality.The type alias mechanism should be extended to give special meaning to a mapping of a {{Runtime}} type to a Puppet Type. The semantics of this is "this runtime type is a representation of this puppet type".As an example - this is what puppet uses internally:{code :puppet }type Runtime[ruby, Float] = Float{code}By making it possible to specify these mappings, there is nothing special or secret about any of the mappings. Serialization simply refers to a type model to know what the bindings are supposed to be in the implementation that serializes/deserializes.It is of great value to use the pattern in PUP--5928 to also specify the RHS:{code:puppet}type Runtime[ruby, /MyPackage::P(.*)Type/] = [MyModule::MyPackage, "\1"][code}(Or similar syntax). This would mean, all the classes in the Ruby MyPackage that has the pattern PType would be mapped to the corresponding puppet name e.g. MyPackage::PFooType is mapped to MyModule::MyPackage::Foo as a puppet name.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5929
Allow type alias to define a mapping between puppet names and runtime types
Change By:
Thomas Hallgren
When doing serialization between runtimes of different versions or implementation languages it is of value to be able to define the mapping between names in the puppet name space and the implementation that is performing the operation.This relates to PUP-5928 where it is possible to define a pattern so that each class in a package does not have to be stated and instead be matched with a pattern. The functionality in PUP-5928 is used here for further functionality.The type alias mechanism should be extended to give special meaning to a mapping of a {{Runtime}} type to a Puppet Type. The semantics of this is "this runtime type is a representation of this puppet type".As an example - this is what puppet uses internally:{code :puppet }type Runtime[ruby, Float] = Float{code}By making it possible to specify these mappings, there is nothing special or secret about any of the mappings. Serialization simply refers to a type model to know what the bindings are supposed to be in the implementation that serializes/deserializes.It is of great value to use the pattern in PUP--5928 to also specify the RHS:{code:puppet}type Runtime[ruby, /MyPackage::P(.*)Type/] = [MyModule::MyPackage, "\1"] [ { code}(Or similar syntax). This would mean, all the classes in the Ruby MyPackage that has the pattern PType would be mapped to the corresponding puppet name e.g. MyPackage::PFooType is mapped to MyModule::MyPackage::Foo as a puppet name.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5928) Add pattern matching to Runtime Type
Title: Message Title Thomas Hallgren commented on PUP-5928 Re: Add pattern matching to Runtime Type In order for this to be useful, we will have to define a substitution, not just a pattern. 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-5925) Optional data type and data binding with undef as default value
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5925 Optional data type and data binding with undef as default value Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-5925) Optional data type and data binding with undef as default value
Title: Message Title Henrik Lindberg commented on PUP-5925 Re: Optional data type and data binding with undef as default value and merged to master 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-5735) Remove usage of win32-security gem
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-5735 Remove usage of win32-security gem Change By: Glenn Sarti Assignee: Ethan Brown 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-5928) Add pattern matching to Runtime Type
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5928
Add pattern matching to Runtime Type
Change By:
Thomas Hallgren
Currently the {{Runtime}} type can describe only one class at the time. As we plan to use this to provide mappings from general models to an implementation (e.g. to bind AST related classes like Locator, or the AST itself) to puppet names in such a way that implementations in different languages can read/write a data stream where instances are identified by the puppet name), it is onerous having to individually define those mappings (AST =~ 100 classes).To support this, the {{Runtime}} type should provide regular _expression_ support. Currently it only accepts a single classname.{code:puppet}$in_my_package_t = Runtime[ruby, /MyPackage::.*/] ( { code}can then be used to answer if an implementation instance is an instance of that runtime type.
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-5925) Optional data type and data binding with undef as default value
Title: Message Title Henrik Lindberg commented on PUP-5925 Re: Optional data type and data binding with undef as default value merged to stable: 9319d1a 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-5925) Optional data type and data binding with undef as default value
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5925 Optional data type and data binding with undef as default value Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5929 Allow type alias to define a mapping between puppet names and runtime types Issue Type: New Feature Assignee: Unassigned Created: 2016/02/19 9:53 AM Fix Versions: PUP 4.x Priority: Normal Reporter: Henrik Lindberg When doing serialization between runtimes of different versions or implementation languages it is of value to be able to define the mapping between names in the puppet name space and the implementation that is performing the operation. This relates to PUP-5928 where it is possible to define a pattern so that each class in a package does not have to be stated and instead be matched with a pattern. The functionality in PUP-5928 is used here for further functionality. The type alias mechanism should be extended to give special meaning to a mapping of a Runtime type to a Puppet Type. The semantics of this is "this runtime type is a representation of this puppet type". As an example - this is what puppet uses internally: type Runtime[ruby, Float] = Float
Jira (PUP-5914) data binding: a way to set the merge behaviour (like in the lookup() function) ?
Title: Message Title Henrik Lindberg commented on PUP-5914 Re: data binding: a way to set the merge behaviour (like in the lookup() function) ? And you are right lookup_options is an exception to the rule that you can only bind values in the module's name space. It is also a reserved key - you cannot use lookup to get the value of lookup_options. 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-5914) data binding: a way to set the merge behaviour (like in the lookup() function) ?
Title: Message Title Henrik Lindberg commented on PUP-5914 Re: data binding: a way to set the merge behaviour (like in the lookup() function) ? IIRC, lookup_options are merged, but if you specify a key, it's content wins over lower levels. This means that all keys that are specified at any layer contribute to the overall lookup_options, but specification at a higher level of the same key as at a lower level wins. (I may have missed some detail, but that is the principle). 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-5925) Optional data type and data binding with undef as default value
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5925 Optional data type and data binding with undef as default value Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-5925) Optional data type and data binding with undef as default value
Title: Message Title Henrik Lindberg commented on PUP-5925 Re: Optional data type and data binding with undef as default value Francois Lafont You do get special favours since you were an early adopter of the lookup features and using function style data binding . We should be thanking you finding real world problems. (Hint to others: you do get favours if you dare to live on the bleeding edge ) 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-5697) Inline file permissions
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5697 Inline file permissions Change By: William Hopper Status: Ready for CI Test Assignee: qa 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.
