Jira (HI-46) Hiera should support alternate environments
Title: Message Title Henrik Lindberg commented on HI-46 Re: Hiera should support alternate environments I am curious about the use case query across all environments - what is the purpose of that? As I see it that seems to imply asking for what is the value of parameter x::y::z for node n if it were in any of the currently known environments - such a query cannot be answered without evaluating the puppet logic since it may lookup with different strategies (not all parameters get their value with priority lookup). If we take the node out of the equation - it is clearly possible to just iterate over all the known environments and lookup a key; it does not however then know which module to use for default values - it could guess module based on the fully qualified name, which would be correct most of the time (i.e. unless someone instantiates something that is outside of a module's name space). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4025) Module tool should give more details about forge errors
Title: Message Title Anderson Mills updated an issue Puppet / PUP-4025 Module tool should give more details about forge errors Change By: Anderson Mills Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Nicholas Fagerlund commented on PUP-1073 Re: Support common package name in two different providers From an explainability standpoint, I think it's perfectly reasonable to say that resource types with composite namevars just can't take advantage of automatic reference aliasing, and you need to use the title to refer to them. Auto aliasing always seemed like kind of a misfeature to me in the first place, tbh; too magical. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Nicholas Fagerlund updated an issue Hiera / HI-274 :merge_behavior with deep_merge gem missing should error instead of falling back Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Nicholas Fagerlund commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Henrik Lindberg from a user's perspective, I consider that a straight-up bug fix. We'll want to mention it in the release notes, but that's the only docs impact. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1132) the events endpoint should not require a query
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1132 the events endpoint should not require a query Change By: Wyatt Alt Sprint: PuppetDB2015-02-25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4020) A way to ask a resource what the type of its parameters are
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4020 A way to ask a resource what the type of its parameters are Change By: Henrik Lindberg Fix Version/s: PUP4.x Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-1073
Support common package name in two different providers
Change By:
Michael Smith
Ihaveacommonpackagename,that'sintwodifferentpackagemanagers(onewithyumtheotherwithgem){code}package{remove-mysql:name=mysql,provider=yum,ensure=absent,}{code}-{code}package{gem-mysql:name=mysql,ensure=2.7,provider=gem,}{code}-Igetthiserror.{noformat}Jul308:43:34puppetd[11872]:Couldnotretrievecatalog:Puppet::Parser::AST::ResourcefailedwitherrorArgumentError:CannotaliasPackage[gem-mysql]tomysql;resourcePackage[mysql]alreadyexistsat/etc/puppet/modules/ruby-mysql/manifests/init.pp:11onnode{noformat}Thesolutiontothiswastogenerateauniquenesskeybasedon{{\[name,provider\]}},asmentionedby[~andy].Thatallowstheexampleabovetowork,butdoesn'tresolvewhenmultipleprovidersmanagethesamepackage.Severalchangeswereneeded:#Set{{paramclass(:provider).isnamevar}}onthePackagetype,sothe{{:provider}}parameterisrecognizedaspartofthenamevar.#Overloadedthe{{title_patterns}}methodonthePackagetype,sothe{{title}}couldbeparsedintonamevars(itonlysets{{:name}},not{{:provider}}).#The{{catalog}}assumedthatisomorphicresourcesonlyneededtobealiasedifthe{{title}}and{{name}}didn'tmatch.Analiasisautomaticallycreatedforaresource's{{title}};if{{titles}}don'tmatchbutthe{{namevar}}doestheyshouldstillrefertothesamething.However,{{name}}isnotequivalentto{{namevar}}fora{{compositenamevar}},sothetestforwhethertocreateanaliasusesthe{{uniqueness_key}}(anarraycontainingall{{namevars}}).Theimpactofthischangeistocorrectlyidentifywhenaresourcewitha{{compositenamevar}}hasalreadybeencreated,asin{code}package{add-mysql:name=mysql,ensure=present,}package{mysql:ensure=present,}{code} #The{{uniqueness_key}}implementationin{{resource}}typeassumedeither Changes(1)and(2)arerequiredforanyproviderthatusesacompositenamevar.Unfinishedworkincludes*Queryingresourcesbynameonthecommand-linewhenmultiplepackagesfromdifferentprovidersarespecified(PUP-3721).*ReferringtoPackageresourcesby{{Package[$namevar]}}inPuppetcodedoesn'tworkfora{{compositenamevar}},soitnolongerworksforPackage.Queryingby{{Package[$title]}}stillworks.ThisisabreakingchangeinPuppet4.
Add Comment
Jira (PDB-1224) Move fact path reference from the fact_values table to the facts table
Title: Message Title Rob Browning commented on PDB-1224 Re: Move fact path reference from the fact_values table to the facts table Tested several approaches and settled on creating a migration facts table explicitly from scratch for now. We just drop the dead columns from the other tables since that should be quite cheap with postgresql. Current version of the code should be here: https://github.com/rbrw/puppetdb/compare/ticket/master/pdb-1224-lift-fact-paths-into-facts Note that this code will break puppetdb until PDB-1225 is ready. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1225) Update fact storage and querying to use the new path column in the facts table
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1225 Update fact storage and querying to use the new path column in the facts table Change By: Rob Browning Assignee: RobBrowning Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Christopher Price updated an issue Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Christopher Price Sprint: Server SERVER 2015-04- 01 15 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1073 Support common package name in two different providers Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-1073
Support common package name in two different providers
Change By:
Michael Smith
Ihaveacommonpackagename,that'sintwodifferentpackagemanagers(onewithyumtheotherwithgem){code}package{remove-mysql:name=mysql,provider=yum,ensure=absent,}{code}-{code}package{gem-mysql:name=mysql,ensure=2.7,provider=gem,}{code}-Igetthiserror.{noformat}Jul308:43:34puppetd[11872]:Couldnotretrievecatalog:Puppet::Parser::AST::ResourcefailedwitherrorArgumentError:CannotaliasPackage[gem-mysql]tomysql;resourcePackage[mysql]alreadyexistsat/etc/puppet/modules/ruby-mysql/manifests/init.pp:11onnode{noformat}Thesolutiontothiswastogenerateauniquenesskeybasedon{{\[name,provider\]}},asmentionedby[~andy].Thatallowstheexampleabovetowork,butdoesn'tresolvewhenmultipleprovidersmanagethesamepackage.Severalchangeswereneeded:#Set{{paramclass(:provider).isnamevar}}onthePackagetype,sothe{{:provider}}parameterisrecognizedaspartofthenamevar.#Overloadedthe{{title_patterns}}methodonthePackagetype,sothe{{title}}couldbeparsedintonamevars(itonlysets{{:name}},not{{:provider}}).#The{{catalog}}assumedthatisomorphicresourcesonlyneededtobealiasedifthe{{title}}and{{name}}didn'tmatch.Analiasisautomaticallycreatedforaresource's{{title}};if{{titles}}don'tmatchbutthe{{namevar}}doestheyshouldstillrefertothesamething.However,{{name}}isnotequivalentto{{namevar}}fora{{compositenamevar}},sothetestforwhethertocreateanaliasusesthe{{uniqueness_key}}(anarraycontainingall{{namevars}}).Theimpactofthischangeistocorrectlyidentifywhenaresourcewitha{{compositenamevar}}hasalreadybeencreated,asin{code}package{add-mysql:name=mysql,ensure=present,}package{mysql:ensure=present,}{code}#Thechangeto{{catalog}} meant means thatcreatingaliasesnow dependen depends onthe{{uniqueness_key}}.Thatimplementationin{{resource}}typecouldendupreturninganarraywithoutthenamespecifiedifthe{{:name}}parameterwasn'tspecificallyspecified.Idon'trecall whythismattersyet,stillfiguringout the testcasethatdemonstratedaproblem visibleimpactofthis .Changes(1)and(2)arerequiredforanyproviderthatusesacompositenamevar.Impactofthischange:*Queryingresourcesbynameonthecommand-linewhenmultiplepackagesfromdifferentprovidersarespecifiedonlyreturnsthepackagewiththedefaultprovider(PUP-3721).*ReferringtoPackageresourcesby{{Package[$namevar]}}inPuppetcodedoesn'tworkfora{{compositenamevar}},soitnolongerworksforPackage.Queryingby{{Package[$title]}}stillworks.ThisisabreakingchangeinPuppet4.
Add Comment
Jira (PDB-1240) PR (1261): Bump to latest ezbake plugin - kbarber
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-1240 PR (1261): Bump to latest ezbake plugin - kbarber Change By: Kenneth Barber Assignee: KennethBarber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1240) PR (1261): Bump to latest ezbake plugin - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1240 PR (1261): Bump to latest ezbake plugin - kbarber Change By: Kenneth Barber Fix Version/s: PDB3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1240) PR (1261): Bump to latest ezbake plugin - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1240 PR (1261): Bump to latest ezbake plugin - kbarber Issue Type: Task Assignee: Unassigned Created: 2015/02/17 5:30 PM Labels: github Priority: Normal Reporter: gepetto-bot Bump to latest ezbake plugin Author: Ken Barber k...@bob.sh Company: Puppet Labs Inc. Github ID: kbarber Pull Request 1261 Discussion Pull Request 1261 File Diff Pull Request Description This bumps us to use ezbake 0.2.2, which at the very least solves logrotate pathing mistakes in 0.2.1. Signed-off-by: Ken Barber k...@bob.sh
Jira (PDB-1240) PR (1261): Bump to latest ezbake plugin - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1240 PR (1261): Bump to latest ezbake plugin - kbarber Change By: Kenneth Barber Sprint: PuppetDB2015-02-25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-1073
Support common package name in two different providers
Change By:
Michael Smith
Ihaveacommonpackagename,that'sintwodifferentpackagemanagers(onewithyumtheotherwithgem){code}package{remove-mysql:name=mysql,provider=yum,ensure=absent,}{code}-{code}package{gem-mysql:name=mysql,ensure=2.7,provider=gem,}{code}-Igetthiserror.{noformat}Jul308:43:34puppetd[11872]:Couldnotretrievecatalog:Puppet::Parser::AST::ResourcefailedwitherrorArgumentError:CannotaliasPackage[gem-mysql]tomysql;resourcePackage[mysql]alreadyexistsat/etc/puppet/modules/ruby-mysql/manifests/init.pp:11onnode{noformat}Thesolutiontothiswastogenerateauniquenesskeybasedon{{\[name,provider\]}},asmentionedby[~andy].Thatallowstheexampleabovetowork,butdoesn'tresolvewhenmultipleprovidersmanagethesamepackage.Severalchangeswereneeded:#Set{{paramclass(:provider).isnamevar}}onthePackagetype,sothe{{:provider}}parameterisrecognizedaspartofthenamevar.#Overloadedthe{{title_patterns}}methodonthePackagetype,sothe{{title}}couldbeparsedintonamevars(itonlysets{{:name}},not{{:provider}}).#The{{catalog}}assumedthatisomorphicresourcesonlyneededtobealiasedifthe{{title}}and{{name}}didn'tmatch.Analiasisautomaticallycreatedforaresource's{{title}};if{{titles}}don'tmatchbutthe{{namevar}}doestheyshouldstillrefertothesamething.However,{{name}}isnotequivalentto{{namevar}}fora{{compositenamevar}},sothetestforwhethertocreateanaliasusesthe{{uniqueness_key}}(anarraycontainingall{{namevars}}).Theimpactofthischangeistocorrectlyidentifywhenaresourcewitha{{compositenamevar}}hasalreadybeencreated,asin{code}package{add-mysql:name=mysql,ensure=present,}package{mysql:ensure=present,}{code}#The changeto {{ catalog}}meantthatcreatingaliasesnowdependenonthe{{ uniqueness_key}} .That implementationin{{resource}}type assumedeither couldendupreturninganarraywithoutthenamespecifiedifthe{{:name}}parameterwasn'tspecificallyspecified. Changes(1)and(2)arerequiredforanyproviderthatusesacompositenamevar.Unfinishedworkincludes*Queryingresourcesbynameonthecommand-linewhenmultiplepackagesfromdifferentprovidersarespecified(PUP-3721).*ReferringtoPackageresourcesby{{Package[$namevar]}}inPuppetcodedoesn'tworkfora{{compositenamevar}},soitnolongerworksforPackage.Queryingby{{Package[$title]}}stillworks.ThisisabreakingchangeinPuppet4.
Add Comment
Jira (PDB-1239) PR (1258): Remove pinning against a git sha1 for beaker now ezbake helpers have been released - kbarber
Title: Message Title gepetto-bot commented on PDB-1239 Re: PR (1258): Remove pinning against a git sha1 for beaker now ezbake helpers have been released - kbarber Pull request Remove pinning against a git sha1 for beaker now ezbake helpers have been released has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-1073
Support common package name in two different providers
Change By:
Michael Smith
Ihaveacommonpackagename,that'sintwodifferentpackagemanagers(onewithyumtheotherwithgem){code}package{remove-mysql:name=mysql,provider=yum,ensure=absent,}{code}-{code}package{gem-mysql:name=mysql,ensure=2.7,provider=gem,}{code}-Igetthiserror.{noformat}Jul308:43:34puppetd[11872]:Couldnotretrievecatalog:Puppet::Parser::AST::ResourcefailedwitherrorArgumentError:CannotaliasPackage[gem-mysql]tomysql;resourcePackage[mysql]alreadyexistsat/etc/puppet/modules/ruby-mysql/manifests/init.pp:11onnode{noformat}Thesolutiontothiswastogenerateauniquenesskeybasedon{{\[name,provider\]}},asmentionedby[~andy].Thatallowstheexampleabovetowork,butdoesn'tresolvewhenmultipleprovidersmanagethesamepackage.Severalchangeswereneeded:#Set{{paramclass(:provider).isnamevar}}onthePackagetype,sothe{{:provider}}parameterisrecognizedaspartofthenamevar.#Overloadedthe{{title_patterns}}methodonthePackagetype,sothe{{title}}couldbeparsedintonamevars(itonlysets{{:name}},not{{:provider}}).#The{{catalog}}assumedthatisomorphicresourcesonlyneededtobealiasedifthe{{title}}and{{name}}didn'tmatch.Analiasisautomaticallycreatedforaresource's{{title}};if{{titles}}don'tmatchbutthe{{namevar}}doestheyshouldstillrefertothesamething.However,{{name}}isnotequivalentto{{namevar}}fora{{compositenamevar}},sothetestforwhethertocreateanaliasusesthe{{uniqueness_key}}(anarraycontainingall{{namevars}}).Theimpactofthischangeistocorrectlyidentifywhenaresourcewitha{{compositenamevar}}hasalreadybeencreated,asin{code}package{add-mysql:name=mysql,ensure=present,}package{mysql:ensure=present,}{code}#Thechangeto{{catalog}}meantthatcreatingaliasesnowdependenonthe{{uniqueness_key}}.Thatimplementationin{{resource}}typecouldendupreturninganarraywithoutthenamespecifiedifthe{{:name}}parameterwasn'tspecificallyspecified. Idon'trecallwhythismattersyet,stillfiguringoutthetestcasethatdemonstratedaproblem. Changes(1)and(2)arerequiredforanyproviderthatusesacompositenamevar.Unfinishedworkincludes*Queryingresourcesbynameonthecommand-linewhenmultiplepackagesfromdifferentprovidersarespecified(PUP-3721).*ReferringtoPackageresourcesby{{Package[$namevar]}}inPuppetcodedoesn'tworkfora{{compositenamevar}},soitnolongerworksforPackage.Queryingby{{Package[$title]}}stillworks.ThisisabreakingchangeinPuppet4.
Add Comment
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Henrik Lindberg commented on PUP-1073 Re: Support common package name in two different providers Yes, whatever is specified is evaluated, turned into an array and flattened - then each entry becomes one reference. It is common to do things like Package[$a, $b] where $a and $b are arrays of titles. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-282) hiera binary with `-i nodename.domain.com` fails under puppet 3
Title: Message Title Henrik Lindberg commented on HI-282 Re: hiera binary with `-i nodename.domain.com` fails under puppet 3 Hiera 2.0 (hiera master) only works with Puppet 4.0 and there the inventory service has been removed since it is deprecated in Puppet 3x. Hiera 2.0 will be packaged as part of AIO (all in one agent) and it is done for Puppet 4.0. What we really want to do is ensure that the -i option is removed from the hiera command completely. Since it does not work in 3.x anyway, it can just be removed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Nicholas Fagerlund not sure if docs need to change - the behavior is now that there is an error if a deep merge is requested and the gem is not present. Earlier it was only a warning, and unexpected data was returned. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1132) the events endpoint should not require a query
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1132 the events endpoint should not require a query Change By: Kenneth Barber Fix Version/s: PDB3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4027) Update embedded docs for package resource type in light of PUP-1073
Title: Message Title Michael Smith moved an issue Puppet / PUP-4027 Update embedded docs for package resource type in light of PUP-1073 Change By: Michael Smith Scrum Team: ClientPlatform Component/s: PuppetLanguage Component/s: Language Component/s: DOCS Workflow: Documentation Platform Workflow Key: DOC PUP - 1661 4027 Project: Documentation[Internal] Puppet Add Comment
Jira (PUP-4027) Update embedded docs for package resource type in light of PUP-1073
Title: Message Title Michael Smith updated an issue Puppet / PUP-4027 Update embedded docs for package resource type in light of PUP-1073 Change By: Michael Smith Sprint: Client2015-03-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Michael Smith updated an issue Puppet / PUP-1073 Support common package name in two different providers Change By: Michael Smith Sprint: PlatformClient2014-11-26,PlatformClient2014-12-17,PlatformClient2015-01-07,PlatformClient2015-01-21,Client2015- 03 02 - 04 18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Michael Smith updated an issue Puppet / PUP-1073 Support common package name in two different providers Change By: Michael Smith Sprint: PlatformClient2014-11-26,PlatformClient2014-12-17,PlatformClient2015-01-07,PlatformClient2015-01-21 ,Client2015-02-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1228) investigate a paging solution for multi-row responses
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-1228 investigate a paging solution for multi-row responses Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Henrik Lindberg commented on PUP-1073 Re: Support common package name in two different providers So, if someone wanted to make a reference it would need to be done like Package[$provider-$namevar] for the Package type, knowing that it maps that way to title. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Also note that Hiera 2.0.0 will be shipped using the AIO packaging where the deep merge gem is included. (In 4.0.0 Puppet also depends on that gem being present). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-274 :merge_behavior with deep_merge gem missing should error instead of falling back Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4022) Make classes and defined types discoverable through RAL
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-4022 Make classes and defined types discoverable through RAL Change By: Henrik Lindberg Assignee: HenrikLindberg Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-282) hiera binary with `-i nodename.domain.com` fails under puppet 3
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-282
hiera binary with `-i nodename.domain.com` fails under puppet 3
Change By:
Henrik Lindberg
duetochangesinthesettingsinitializationsystem,usingthe`-i`flag(queryinventoryservice)fromthehierabinarycausesanexceptionwithpuppet3.0.0andabove: pre {code} [eric@glitch.local~/Sandbox]%/Users/eric/Sandbox/hiera/bin/hierasysadmin--config/Users/eric/Sandbox/explosive-puppet/hiera.yaml-iglitch.localPuppetinventoryservicelookupfailed:NoMethodError:undefinedmethod`features'forPuppet:ModuleCouldnotloadPuppetinventoryservicescope:SystemExit:exit /pre {code} Youcansomewhathackaroundthisbymovingtothenew`Puppet.initialize_settings`methodinsteadof`Puppet.Settings.parse_config`,asinthefollowingpatch,butthatishardcodedtoloadsettingsforthe`:user`run_mode,soyoulosetheabilitytogetthe`[master]`section'ssettings. pre {code} diff--gita/bin/hierab/bin/hieraindexddd4daa..1814351100755---a/bin/hiera+++b/bin/hiera@@-91,10+91,8@@defload_scope(source,type=:yaml)#isfinetohavetheinventory_serveroptionseteveniftheconfig#doesn'thavethefact_terminussettorest.begin-require'puppet/util/run_mode'-$puppet_application_mode=Puppet::Util::RunMode[:master]require'puppet'-Puppet.settings.parse+Puppet.initialize_settingsPuppet::Node::Facts.indirection.terminus_class=:restscope=YAML.load(Puppet::Node::Facts.indirection.find(source).to_yaml)#Puppetmakesdumbyamlfilesthatdonotpromotedatareuse. /pre {code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-274 :merge_behavior with deep_merge gem missing should error instead of falling back Change By: Henrik Lindberg Sprint: Language2015-02-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Merged to master https://github.com/puppetlabs/hiera/commit/17afe9761a2c97feacb58d1d7e88201dbb3d Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-274 :merge_behavior with deep_merge gem missing should error instead of falling back Change By: Henrik Lindberg Fix Version/s: HI2.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-339) allow for strict or validated mode for backend
Title: Message Title dave ingham created an issue Hiera / HI-339 allow for strict or validated mode for backend Issue Type: New Feature Assignee: Unassigned Created: 2015/02/17 4:54 PM Priority: Normal Reporter: dave ingham Hiera allows for a variety of backends. If a piece of data is not found from a backend, the search continues in the next backend. This makes sense as the data may be in a different file or a different data source. If the data source fails (such as a malformed YAML file or a broken database connection), the system will silently traverse. This a relaxed and forgiving approach that would likely work in many scenarios. It would be ideal, if the a backend (or hierarchy) could be specified in a strict mode. In this mode, the data sought may not be in a particular source but the source must exists. Ideally the same type of datastore could be added in the default mode. This would allow for some hierarchies to be strict and others to be relaxed. Add Comment
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Henrik Lindberg commented on HI-46 Re: Hiera should support alternate environments This ticket is turning out to be a good discussion about use cases and requirements. (I like that). To recap and talk about the ideas going forward. PUP-1640 adds the mechanism with which it is possible to provide data that is environment specific, and that is specific to a module. PUP-3948 makes the lookup function the consolidated lookup mechanism (it looks up in global hiera, in data from the environment, and in a module, and it can do the types of merges and tricks that the combined functions hiera, hiera_array, and hiera_hash can do (and a little bit more). The function does this without having a direct dependency on hiera - only on the current Data Binding API, and the new Data Provider API. In practice this means that much data that is now in a single hierarchy for all environments can migrate to be environment specific (or indeed migrate to modules if they are defaults for modules). Then the global data will be used for site specific data or environment overrides/amends. This should help flowing a version of a configuration from a dev env to a test env to a production env on the same or different masters. The new approach allows having a separate hierarchy in the environment - it does not even have to be hiera based (if/when/where that makes more sense). After 4.0.0 is out, I want us to refactor hiera so it functions under the Data Provider API (i.e. that it no longer is a singleton (== strictly global). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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
Jira (PUP-4025) Module tool should give more details about forge errors
Title: Message Title Ryan Coleman commented on PUP-4025 Re: Module tool should give more details about forge errors Yup, sorry Matthaus Owens. My attempt to be helpful was not very helpful. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Nicholas Fagerlund commented on PUP-1073 Re: Support common package name in two different providers Michael Smith Yo, unless there's anything else you were meaning to mention here, I consider that an awesome description update and a finished ticket. I'll start filing docs tickets for all the work this represents, and you can re-close this one once you're pretty sure you've finished the brain dump. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1329) composite namevars should be more robust
Title: Message Title Nicholas Fagerlund commented on PUP-1329 Re: composite namevars should be more robust composite namevars should be purgable - I'm not sure what this means With the resources resource type, you can purge unmanaged instances of any resource type that (I think!) is ensurable and implements self.instances —Puppet will actually discover every resource of that type, and set it to ensure = absent if there isn't a resource declaration managing it. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Henrik Lindberg commented on PUP-1073 Re: Support common package name in two different providers Why not just let the user set whatever unique title they like (that is the reference and it must be unique), and then set name and provider either automatically by parsing the title, or manually setting them to whatever is needed. That way, title is specified, it must be unique - internally name+provider must be unique. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4020) Add a Like type to specify a type being the type of a resource parameter
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4020
Add a Like type to specify a type being the type of a resource parameter
Change By:
Henrik Lindberg
AswediscussedpreviouslyonIRCandlastnightattheStockholmPUG,itwouldbenicetobeabletoaskaclassor(defined)typewhatthetypeofitsparametersare.Forexample,ifyou'rewrappingsomethinglike{{apache::vhost}}andareexposingparametersthatgetpassedthrough1:1itwouldbenicetobeabletotellyourclassthisparameterneedstoadheretothesametypeasthatparameteron{{apache::vhost}}.Ideallyweshouldalsobeabletodothisfornativetypesoncethey'vebeenrewrittentoactuallyprovidetypeinformation,sothatwhenyouexposea{{packages_ensure}}parameteronyourclassyoucangiveitatype_expression_alongthelinesof{{Package.ensure$packages_ensure='present'}}. UpdateWecametotheconclusionthatthisisbestdonebyintroducingatypeinthetypesystem{{Like}}thatisparameterizedwithtwovalues,thenameofatype(defaultaresourcetype),andaparametername.Theresultisthetypeofthatparameter.Thefirsttypecanalsobeexpressedusingatype(i.e.Resource[type],Class[name]).Thisopenstheabilityalsoreferencethetypeparametersofothertypessuchasthefrom/toparametersinanIntegertype,thevariantsofavarianttype,etc.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-1073
Support common package name in two different providers
Change By:
Michael Smith
Ihaveacommonpackagename,that'sintwodifferentpackagemanagers(onewithyumtheotherwithgem){code}package{remove-mysql:name=mysql,provider=yum,ensure=absent,}{code}-{code}package{gem-mysql:name=mysql,ensure=2.7,provider=gem,}{code}-Igetthiserror.{noformat}Jul308:43:34puppetd[11872]:Couldnotretrievecatalog:Puppet::Parser::AST::ResourcefailedwitherrorArgumentError:CannotaliasPackage[gem-mysql]tomysql;resourcePackage[mysql]alreadyexistsat/etc/puppet/modules/ruby-mysql/manifests/init.pp:11onnode{noformat}Thesolutiontothiswastogenerateauniquenesskeybasedon{{\[name,provider\]}},asmentionedby[~andy].Thatallowstheexampleabovetowork,butdoesn'tresolvewhenmultipleprovidersmanagethesamepackage.Severalchangeswereneeded:#Set{{paramclass(:provider).isnamevar}}onthePackagetype,sothe{{:provider}}parameterisrecognizedaspartofthenamevar.#Overloadedthe{{title_patterns}}methodonthePackagetype,sothe{{title}}couldbeparsedintonamevars(itonlysets{{:name}},not{{:provider}}).#The{{catalog}}assumedthatisomorphicresourcesonlyneededtobealiasedifthe{{title}}and{{name}}didn'tmatch.Analiasisautomaticallycreatedforaresource's{{title}};if{{titles}}don'tmatchbutthe{{namevar}}doestheyshouldstillrefertothesamething.However,{{name}}isnotequivalentto{{namevar}}fora{{compositenamevar}},sothetestforwhethertocreateanaliasusesthe{{uniqueness_key}}(anarraycontainingall{{namevars}}).Theimpactofthischangeistocorrectlyidentifywhenaresourcewitha{{compositenamevar}}hasalreadybeencreated,asin{code}package{add-mysql:name=mysql,ensure=present,}package{mysql:ensure=present,}{code}#Thechangeto{{catalog}}meantthatcreatingaliasesnowdependenonthe{{uniqueness_key}}.Thatimplementationin{{resource}}typecouldendupreturninganarraywithoutthenamespecifiedifthe{{:name}}parameterwasn'tspecificallyspecified.Idon'trecallwhythismattersyet,stillfiguringoutthetestcasethatdemonstratedaproblem.Changes(1)and(2)arerequiredforanyproviderthatusesacompositenamevar.Impactofthischange:*Queryingresourcesbynameonthecommand-linewhenmultiplepackagesfromdifferentprovidersarespecified doesn'twork onlyreturnsthepackagewiththedefaultprovider (PUP-3721).*ReferringtoPackageresourcesby{{Package[$namevar]}}inPuppetcodedoesn'tworkfora{{compositenamevar}},soitnolongerworksforPackage.Queryingby{{Package[$title]}}stillworks.ThisisabreakingchangeinPuppet4.
Add Comment
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-1073
Support common package name in two different providers
Change By:
Michael Smith
Ihaveacommonpackagename,that'sintwodifferentpackagemanagers(onewithyumtheotherwithgem){code}package{remove-mysql:name=mysql,provider=yum,ensure=absent,}{code}-{code}package{gem-mysql:name=mysql,ensure=2.7,provider=gem,}{code}-Igetthiserror.{noformat}Jul308:43:34puppetd[11872]:Couldnotretrievecatalog:Puppet::Parser::AST::ResourcefailedwitherrorArgumentError:CannotaliasPackage[gem-mysql]tomysql;resourcePackage[mysql]alreadyexistsat/etc/puppet/modules/ruby-mysql/manifests/init.pp:11onnode{noformat}Thesolutiontothiswastogenerateauniquenesskeybasedon{{\[name,provider\]}},asmentionedby[~andy].Thatallowstheexampleabovetowork,butdoesn'tresolvewhenmultipleprovidersmanagethesamepackage.Severalchangeswereneeded:#Set{{paramclass(:provider).isnamevar}}onthePackagetype,sothe{{:provider}}parameterisrecognizedaspartofthenamevar.#Overloadedthe{{title_patterns}}methodonthePackagetype,sothe{{title}}couldbeparsedintonamevars(itonlysets{{:name}},not{{:provider}}).#The{{catalog}}assumedthatisomorphicresourcesonlyneededtobealiasedifthe{{title}}and{{name}}didn'tmatch.Analiasisautomaticallycreatedforaresource's{{title}};if{{titles}}don'tmatchbutthe{{namevar}}doestheyshouldstillrefertothesamething.However,{{name}}isnotequivalentto{{namevar}}fora{{compositenamevar}},sothetestforwhethertocreateanaliasusesthe{{uniqueness_key}}(anarraycontainingall{{namevars}}).Theimpactofthischangeistocorrectlyidentifywhenaresourcewitha{{compositenamevar}}hasalreadybeencreated,asin{code}package{add-mysql:name=mysql,ensure=present,}package{mysql:ensure=present,}{code}#Thechangeto{{catalog}}meantthatcreatingaliasesnowdependenonthe{{uniqueness_key}}.Thatimplementationin{{resource}}typecouldendupreturninganarraywithoutthenamespecifiedifthe{{:name}}parameterwasn'tspecificallyspecified.Idon'trecallwhythismattersyet,stillfiguringoutthetestcasethatdemonstratedaproblem.Changes(1)and(2)arerequiredforanyproviderthatusesacompositenamevar.Impactofthischange:*Queryingresourcesbynameonthecommand-linewhenmultiplepackagesfromdifferentprovidersarespecified doesn'twork (PUP-3721).*ReferringtoPackageresourcesby{{Package[$namevar]}}inPuppetcodedoesn'tworkfora{{compositenamevar}},soitnolongerworksforPackage.Queryingby{{Package[$title]}}stillworks.ThisisabreakingchangeinPuppet4.
Add Comment
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Henrik Lindberg commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found Merged to master at: https://github.com/puppetlabs/hiera/commit/83c81c14a90ba453b72955057597c7a485c339a3 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-337 Hiera Backends should distinguish key with null value from key not found Change By: Henrik Lindberg Fix Version/s: HI2.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1132) the events endpoint should not require a query
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1132 the events endpoint should not require a query Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Nicholas Fagerlund updated an issue Hiera / HI-274 :merge_behavior with deep_merge gem missing should error instead of falling back Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-1073
Support common package name in two different providers
Change By:
Michael Smith
Ihaveacommonpackagename,that'sintwodifferentpackagemanagers(onewithyumtheotherwithgem){code}package{remove-mysql:name=mysql,provider=yum,ensure=absent,}{code}-{code}package{gem-mysql:name=mysql,ensure=2.7,provider=gem,}{code}-Igetthiserror.{noformat}Jul308:43:34puppetd[11872]:Couldnotretrievecatalog:Puppet::Parser::AST::ResourcefailedwitherrorArgumentError:CannotaliasPackage[gem-mysql]tomysql;resourcePackage[mysql]alreadyexistsat/etc/puppet/modules/ruby-mysql/manifests/init.pp:11onnode{noformat}Thesolutiontothiswastogenerateauniquenesskeybasedon{{\[name,provider\]}},asmentionedby[~andy].Thatallowstheexampleabovetowork,butdoesn'tresolvewhenmultipleprovidersmanagethesamepackage.Severalchangeswereneeded:#Set{{paramclass(:provider).isnamevar}}onthePackagetype,sothe{{:provider}}parameterisrecognizedaspartofthenamevar.#Overloadedthe{{title_patterns}}methodonthePackagetype,sothe{{title}}couldbeparsedintonamevars(itonlysets{{:name}},not{{:provider}}).#The{{catalog}}assumedthatisomorphicresourcesonlyneededtobealiasedifthe{{title}}and{{name}}didn'tmatch.Analiasisautomaticallycreatedforaresource's{{title}};if{{titles}}don'tmatchbutthe{{namevar}}doestheyshouldstillrefertothesamething.However,{{name}}isnotequivalentto{{namevar}}fora{{compositenamevar}},sothetestforwhethertocreateanaliasusesthe{{uniqueness_key}}(anarraycontainingall{{namevars}}).Theimpactofthischangeistocorrectlyidentifywhenaresourcewitha{{compositenamevar}}hasalreadybeencreated,asin{code}package{add-mysql:name=mysql,ensure=present,}package{mysql:ensure=present,}{code}#Thechangeto{{catalog}}meansthatcreatingaliasesnowdependsonthe{{uniqueness_key}}.Thatimplementationin{{resource}}typecouldendupreturninganarraywithoutthenamespecifiedifthe{{:name}}parameterwasn'tspecificallyspecified. Idon'trecallthevisibleimpact Thischangewasmadesoconflictsbetweenimplicitandexplicitdefaultprovideraredetectedatcatalogcompilationinstead of this tryingtoapplythemanifest .Changes(1)and(2)arerequiredforanyproviderthatusesacompositenamevar.Impactofthischange:*Queryingresourcesbynameonthecommand-linewhenmultiplepackagesfromdifferentprovidersarespecifiedonlyreturnsthepackagewiththedefaultprovider(PUP-3721).*ReferringtoPackageresourcesby{{Package[$namevar]}}inPuppetcodedoesn'tworkfora{{compositenamevar}},soitnolongerworksforPackage.Queryingby{{Package[$title]}}stillworks.ThisisabreakingchangeinPuppet4.
Add Comment
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title Michael Smith commented on PUP-1073 Re: Support common package name in two different providers Supporting Package[$provider-$namevar] seems dangerous as it can collide with existing names. Does Package[[$provider], [$namevar]] already have a meaning? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Support common package name in two different providers
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-1073
Support common package name in two different providers
Change By:
Michael Smith
Ihaveacommonpackagename,that'sintwodifferentpackagemanagers(onewithyumtheotherwithgem){code}package{remove-mysql:name=mysql,provider=yum,ensure=absent,}{code}-{code}package{gem-mysql:name=mysql,ensure=2.7,provider=gem,}{code}-Igetthiserror.{noformat}Jul308:43:34puppetd[11872]:Couldnotretrievecatalog:Puppet::Parser::AST::ResourcefailedwitherrorArgumentError:CannotaliasPackage[gem-mysql]tomysql;resourcePackage[mysql]alreadyexistsat/etc/puppet/modules/ruby-mysql/manifests/init.pp:11onnode{noformat}Thesolutiontothiswastogenerateauniquenesskeybasedon{{\[name,provider\]}},asmentionedby[~andy].Thatallowstheexampleabovetowork,butdoesn'tresolvewhenmultipleprovidersmanagethesamepackage.Severalchangeswereneeded:#Set{{paramclass(:provider).isnamevar}}onthePackagetype,sothe{{:provider}}parameterisrecognizedaspartofthenamevar.#Overloadedthe{{title_patterns}}methodonthePackagetype,sothe{{title}}couldbeparsedintonamevars(itonlysets{{:name}},not{{:provider}}).#The{{catalog}}assumedthatisomorphicresourcesonlyneededtobealiasedifthe{{title}}and{{name}}didn'tmatch.Analiasisautomaticallycreatedforaresource's{{title}};if{{titles}}don'tmatchbutthe{{namevar}}doestheyshouldstillrefertothesamething.However,{{name}}isnotequivalentto{{namevar}}fora{{compositenamevar}},sothetestforwhethertocreateanaliasusesthe{{uniqueness_key}}(anarraycontainingall{{namevars}}).Theimpactofthischangeistocorrectlyidentifywhenaresourcewitha{{compositenamevar}}hasalreadybeencreated,asin{code}package{add-mysql:name=mysql,ensure=present,}package{mysql:ensure=present,}{code}#Thechangeto{{catalog}}meantthatcreatingaliasesnowdependenonthe{{uniqueness_key}}.Thatimplementationin{{resource}}typecouldendupreturninganarraywithoutthenamespecifiedifthe{{:name}}parameterwasn'tspecificallyspecified.Idon'trecallwhythismattersyet,stillfiguringoutthetestcasethatdemonstratedaproblem.Changes(1)and(2)arerequiredforanyproviderthatusesacompositenamevar. Unfinishedworkincludes Impactofthischange: *Queryingresourcesbynameonthecommand-linewhenmultiplepackagesfromdifferentprovidersarespecified(PUP-3721).*ReferringtoPackageresourcesby{{Package[$namevar]}}inPuppetcodedoesn'tworkfora{{compositenamevar}},soitnolongerworksforPackage.Queryingby{{Package[$title]}}stillworks.ThisisabreakingchangeinPuppet4.
Add Comment
Jira (PDB-1099) make the /v4/catalogs endpoint use certname key instead of name
Title: Message Title Wyatt Alt assigned an issue to Russell Mull PuppetDB / PDB-1099 make the /v4/catalogs endpoint use certname key instead of name Change By: Wyatt Alt Assignee: RussellMull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-274 :merge_behavior with deep_merge gem missing should error instead of falling back Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4020) Add a Like type to specify a type being the type of a resource parameter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4020 Add a Like type to specify a type being the type of a resource parameter Change By: Henrik Lindberg Summary: Away AddaLiketype to ask specify a resourcewhat typebeing thetypeof itsparametersare aresourceparameter Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4014) Add PKINIT support to Puppet CA
Title: Message Title Eric Sorenson commented on PUP-4014 Re: Add PKINIT support to Puppet CA Hi Michael Weiser – thanks for this work! It's very interesting but tbh I do not understand much of the operating conditions/constraints that led you to add this feature, so it's tough to say yes we should merge this. (For context, I'm the product manager for Puppet so I try to talk to as many users as possible and balance their problems against engineering constraints to determine the best course of action for the project.) Can you help me understand the environment you're working in and the limitations of the current codebase (especially why you can't use autosign policy+custom CSR attributes) that led you to need this change? From Puppet's perspective, it's a little scary to accept this patch because it changes some deep and not-well-understood parts of the codebase in ways that are not in line with a common use-case, so we really want to make sure we're not going to change behaviour in unexpected ways before merging it. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3957) Packaging improvements for AIO package
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3957 Packaging improvements for AIO package Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3957) Packaging improvements for AIO package
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3957 Packaging improvements for AIO package Change By: Josh Cooper Component/s: RE Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3942) Make sure classifier.yaml is under $confdir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3942 Make sure classifier.yaml is under $confdir Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3957) Packaging improvements for AIO package
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3957 Packaging improvements for AIO package Change By: Josh Cooper Component/s: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3957) Packaging improvements for AIO package
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3957 Packaging improvements for AIO package Change By: Josh Cooper Component/s: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3884) Craft migration/upgrade script for use in the AIO puppet agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3884 Craft migration/upgrade script for use in the AIO puppet agent Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4018) Execute puppet AIO acceptance against puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4018 Execute puppet AIO acceptance against puppetserver Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4019) Add agent role back to the master
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4019 Add agent role back to the master Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4005) AIO agent corrupts CSR extensions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4005 AIO agent corrupts CSR extensions Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4004) Remove acceptance workaround that creates the puppetserver cache related directories
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4004 Remove acceptance workaround that creates the puppetserver cache related directories Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4026) Create specification for new AIO settings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4026 Create specification for new AIO settings Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3997) Audit and update puppet acceptance tests that assume the puppet user and group are present
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3997 Audit and update puppet acceptance tests that assume the puppet user and group are present Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-822) Update Facter to use the virt-what vendored in the AIO agent.
Title: Message Title Josh Cooper updated an issue Facter / FACT-822 Update Facter to use the virt-what vendored in the AIO agent. Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-822) Update Facter to use the virt-what vendored in the AIO agent.
Title: Message Title Josh Cooper assigned an issue to Peter Huene Facter / FACT-822 Update Facter to use the virt-what vendored in the AIO agent. Change By: Josh Cooper Assignee: EricSorenson PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1240) PR (1261): Bump to latest ezbake plugin - kbarber
Title: Message Title gepetto-bot commented on PDB-1240 Re: PR (1261): Bump to latest ezbake plugin - kbarber pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/617/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3809 Separate code (content?) and configuration directories for AIO packaging Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3933) `puppet master --configprint pidfile` returns wrong value for puppetserver (AIO)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3933 `puppet master --configprint pidfile` returns wrong value for puppetserver (AIO) Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3957) Packaging improvements for AIO package
Title: Message Title Josh Cooper assigned an issue to Matthaus Owens Puppet / PUP-3957 Packaging improvements for AIO package Change By: Josh Cooper Assignee: MatthausOwens Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3938) Ruby 2.1.1 needed on Windows 2003 and 2008
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3938 Ruby 2.1.1 needed on Windows 2003 and 2008 Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3944) Make sure puppetdb.conf is under $confdir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3944 Make sure puppetdb.conf is under $confdir Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3943) Make sure console.conf is under $confdir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3943 Make sure console.conf is under $confdir Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4023) Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each'
Title: Message Title Alex Leonhardt updated an issue Puppet / PUP-4023 Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each' Change By: Alex Leonhardt Component/s: CatalogApplication Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4020) A way to ask a resource what the type of its parameters are
Title: Message Title Daniele Sluijters commented on PUP-4020 Re: A way to ask a resource what the type of its parameters are Oh I really Like that one actually. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4020) A way to ask a resource what the type of its parameters are
Title: Message Title
Henrik Lindberg commented on PUP-4020
Re: A way to ask a resource what the type of its parameters are
Yes, we could make the parameter types available automatically - but that creates ambiguities, is A::B::C the type of the parameter 'c' in A::B, or the type A::B::C ? This is essentially the problem I was describing above in the long comment.
I have some other suggestions - we could introduce a type that acts as a reference to another - say Like which could work the same way as the param_type function - e.g:
define( Like[File, ensure] $ensure ) {
...
}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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
Jira (PUP-4005) AIO agent corrupts CSR extensions
Title: Message Title Kylo Ginsberg commented on PUP-4005 Re: AIO agent corrupts CSR extensions Justin May please take a look at this also. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4022) Make classes and defined types discoverable through RAL
Title: Message Title Daniele Sluijters assigned an issue to Henrik Lindberg Puppet / PUP-4022 Make classes and defined types discoverable through RAL Change By: Daniele Sluijters Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4023) Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each'
Title: Message Title Kylo Ginsberg assigned an issue to Alex Leonhardt Puppet / PUP-4023 Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each' Change By: Kylo Ginsberg Assignee: KyloGinsberg AlexLeonhardt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4000) Struct with optional values is not assignable from Hash where key is missing
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4000 Struct with optional values is not assignable from Hash where key is missing Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title Michelle Fredette assigned an issue to Jean Bond Puppet / PUP-3546 Modify exec node terminus to support JSON Change By: Michelle Fredette Assignee: JeanBond Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4018) Execute puppet AIO acceptance against puppetserver
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4018 Execute puppet AIO acceptance against puppetserver Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4019) Add agent role back to the master
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4019 Add agent role back to the master Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4023) Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each'
Title: Message Title Kylo Ginsberg commented on PUP-4023 Re: Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each' Alex Leonhardt no idea. That branch is tested nightly against centos7 so it may be something borked in your install. A couple guesses: can you double check whether you have multiple versions of puppet installed, e.g. by looking with find / -name puppet.rb? are you using any new modules? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1218) Metrics, Status Logs: Add id to reports table
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1218 Metrics, Status Logs: Add id to reports table Change By: AJ Roetker Assignee: AJRoetker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Thomas Hallgren commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found I just submitted a PR. It's done with a keep the change at a minimum mindset. The array case will raise an error since nil is neither a string or an array (as it did before for all other values). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4022) Make classes and defined types discoverable through RAL
Title: Message Title
Daniele Sluijters created an issue
Puppet / PUP-4022
Make classes and defined types discoverable through RAL
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2015/02/17 5:28 AM
Priority:
Normal
Reporter:
Daniele Sluijters
Long shot but, who knows.
It would be nice if you could ask a machine which classes it has and which defined types, similarly to how you can ask a machine about a native type.
puppet resource class apt
apt {
always_update = false
...
Jira (PUP-4023) Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each'
Title: Message Title Alex Leonhardt created an issue Puppet / PUP-4023 Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each' Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Kylo Ginsberg Components: Catalog Application Created: 2015/02/17 7:24 AM Environment: CentOS Linux release 7.0.1406 (Core) ruby 2.0.0p353 (2013-11-22) [x86_64-linux] puppet: 3.7.4 Labels: puppet-agent Priority: Normal Reporter: Alex Leonhardt Hi, I'm seeing the below when running puppet on a new node - it seems that since moving to puppet 3.7.4 on centos 7 (new ruby?) it's unable to find a each method. ``` $ sudo puppet agent -vt Info: Retrieving
Jira (PUP-4017) Make parser an environment specific setting
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-4017 Make parser an environment specific setting Change By: Hailee Kenney Assignee: HaileeKenney Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4025) Module tool should give more details about forge errors
Title: Message Title Ryan Coleman commented on PUP-4025 Re: Module tool should give more details about forge errors Matthaus Owens, I don't think this move was appropriate. IIRC, Alexander Johnson's code management team owns the Puppet Module Tool. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4025) Module tool should give more details about forge errors
Title: Message Title Matthaus Owens commented on PUP-4025 Re: Module tool should give more details about forge errors Ryan Coleman From hipchat: [11:19 AM] Matthaus Owens: @anderson there are no useful affects versions in code management for PMT bugs [11:31 AM] Anderson Mills: @haus Correct. [11:31 AM] Matthaus Owens: @anderson very well [11:31 AM] Anderson Mills: @haus Make a puppet ticket, and then make sure the scrum team is Code Management. [11:31 AM] Matthaus Owens: oh, well then. that is extra confusing :-| [11:31 AM] Anderson Mills: PMT causes code changes in Puppet, so there has to be a Puppet ticket associated with it. Trying to define PMT's home is extra confusing, but this path reduces the number of tickets created. [11:33 AM] Matthaus Owens: @anderson no that's fine, just last friday when i was asking about which project pmt stuff lives in i was told code management, so i feel run around [11:34 AM] Anderson Mills: @haus That is what several of us believed until we realized the PRs need to reference a public ticket. [11:34 AM] Anderson Mills: Scrum team = Code Management, though. [11:37 AM] Matthaus Owens: @anderson https://tickets.puppetlabs.com/browse/PUP-4025 [11:37 AM] Kerminator Frogbot: PUP-4025 Module tool should give more details about forge errors. no assignee / Accepted, no fix version https://tickets.puppetlabs.com/browse/PUP-4025 [11:41 AM] Matthaus Owens: @ryanycoleman you're going to make me cry Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Common package name in two different providers
Title: Message Title Michael Smith commented on PUP-1073 Re: Common package name in two different providers This does appear to be the first resource type with a composite namevar in Puppet core. Package[$title] works fine, but Package[$namevar] no longer works. It would have to look something like Package[$namevar, $provider], and that needs to be addressed in the parser first. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1239) PR (1258): Remove pinning against a git sha1 for beaker now ezbake helpers have been released - kbarber
Title: Message Title gepetto-bot commented on PDB-1239 Re: PR (1258): Remove pinning against a git sha1 for beaker now ezbake helpers have been released - kbarber pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/610/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3821) Use of cfacter on Windows causes error
Title: Message Title
Kurt Wall commented on PUP-3821
Re: Use of cfacter on Windows causes error
Well, at SHA=5bc90e2, there's no seqfault, but there's still an error:
C:\Program Files (x86)\Puppet Labs\Puppet\binpuppet apply --cfacter -e notify
{ 'a': message = 'blarg',}
Error: Could not initialize global default settings: cfacter version 0.2.0 or la
ter is not installed.
C:\Program Files (x86)\Puppet Labs\Puppet\bincfacter --version
0.3.0 (commit 5bc90e28c2e652c86c7debf8086acb61c899c404)
Add Comment
