Jira (FACT-1535) facter --list-cache-groups outputs fact names that I cannot resolve with facter
Title: Message Title Nick Walker commented on FACT-1535 Re: facter --list-cache-groups outputs fact names that I cannot resolve with facter Maggie Dreyer as far as I can tell we don't have any docs on facter.conf and I think we'd want a page on that that would include this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6921) Improve separation of concern between String and Enum types
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6921 Improve separation of concern between String and Enum types Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6884) class parameter default data-syntax and usage for module authors
Title: Message Title Eric Thompson commented on PUP-6884 Re: class parameter default data-syntax and usage for module authors sorry, yes. params.pp (facepalm) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6884) class parameter default data-syntax and usage for module authors
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6884 class parameter default data-syntax and usage for module authors Change By: Eric Thompson Acceptance Criteria: * ensure existing tests cover description.** if no defaults params .pp: ** a class parameter default value(s) come from lookup data ** same value as would have happened with hiera Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6856) data-in-modules: missing facts during building of the hierarchy fails the lookup completely and silently
Title: Message Title Eric Thompson commented on PUP-6856 Re: data-in-modules: missing facts during building of the hierarchy fails the lookup completely and silently i see the unit test for dotted keys in interpolation. do we think we need acceptance tests for the case when missing facts impact hierarchy interpolation, in general? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6834) lookup explain shows found data incorrectly
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6834 lookup explain shows found data incorrectly Change By: Eric Thompson QA Risk Assessment Reason: needs FR, possibly acceptance update covered well in unit tests. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6834) lookup explain shows found data incorrectly
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6834 lookup explain shows found data incorrectly Change By: Eric Thompson QA Risk Assessment Reason: needs FR, possibly acceptance update Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6834) lookup explain shows found data incorrectly
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6834 lookup explain shows found data incorrectly Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1535) facter --list-cache-groups outputs fact names that I cannot resolve with facter
Title: Message Title Maggie Dreyer commented on FACT-1535 Re: facter --list-cache-groups outputs fact names that I cannot resolve with facter I am planning to write up a detailed Confluence page about the new features added with configurable Facter, but is there another place you would like to see better documentation appear? Where do you think would be the most accessible and helpful for customers? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1535) facter --list-cache-groups outputs fact names that I cannot resolve with facter
Title: Message Title Nick Walker commented on FACT-1535 Re: facter --list-cache-groups outputs fact names that I cannot resolve with facter Maggie Dreyer yes I think the output showing which facts are in each group helps clarify. Obviously some docs around it will help too but knowing nothing else the output including the facts under the groups makes it more clear. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6815) Reserved characters in class/type parameters are not enforced
Title: Message Title Jean Bond updated an issue Puppet / PUP-6815 Reserved characters in class/type parameters are not enforced Change By: Jean Bond Labels: docs_reviewed maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp for lookup static data
Title: Message Title Henrik Lindberg commented on PUP-6889 Re: Expressing params.pp for lookup static data Lindsey Smith Yes, in their own time if/when they want to. Don't see class inheritance going away any time soon. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6932) Gem Provider Windows Ruby Path
Title: Message Title Joshua Keiser updated an issue Puppet / PUP-6932 Gem Provider Windows Ruby Path Change By: Joshua Keiser Sort the absolute Ruby path on Windows systems using the Puppet Gem Provider. Currently, puppet ruby is put ahead of anything that already exists in the system PATH which can lead to issues in certain environments. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6932) Gem Provider Windows Ruby Path
Title: Message Title Joshua Keiser created an issue Puppet / PUP-6932 Gem Provider Windows Ruby Path Issue Type: New Feature Assignee: Unassigned Created: 2016/11/17 2:22 PM Priority: Normal Reporter: Joshua Keiser Sort the absolute Ruby path on Windows systems using the Puppet Gem Provider. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1535) facter --list-cache-groups outputs fact names that I cannot resolve with facter
Title: Message Title Maggie Dreyer commented on FACT-1535 Re: facter --list-cache-groups outputs fact names that I cannot resolve with facter See FACT-1536 and associated PR for the mentioned update to the list commands. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6518 puppet resource package kernel reports the wrong rpm version Change By: Moses Mendoza Priority: Minor Normal Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6518 puppet resource package kernel reports the wrong rpm version Change By: Moses Mendoza Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6518 puppet resource package kernel reports the wrong rpm version Change By: Moses Mendoza Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp for lookup static data
Title: Message Title Lindsey Smith commented on PUP-6889 Re: Expressing params.pp for lookup static data The request for an example came from me, maybe a simple params.pp and the equivalent w/functions for lookup. Henrik Lindberg if I understand correctly, migrating from params.pp to lookup is something a user can do incrementally and on their own timeline? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1536) Add top-level facts to output from `--list-X-groups` commands
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Maggie Dreyer Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1536) Add top-level facts to output from `--list-X-groups` commands
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Maggie Dreyer Sprint: AP 2016-11-30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1536) Add top-level facts to output from `--list-X-groups` commands
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) (SPIKE) Find a workflow for POT file generation
Title: Message Title Larissa Lane commented on PUP-6761 Re: (SPIKE) Find a workflow for POT file generation Maggie Dreyer I'll have some more detail about the Transifex integration over the next few days. Things like, can we use a single config file to configure the integration with multiple repos, can we have multiple PO files in a repo, do PO files all need to have a unique file name, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp for lookup static data
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6889 Expressing params.pp for lookup static data Change By: Eric Thompson As a module author currently using the params.pp pattern, I want to use a lookup data provider instead so that not all keys/values have to be computed even if not used so I can make my module perform better.Three key/value function types are supported for data that needs computation:* Data files that directly represents a data structure in json/yaml/hocon (interpolated) ( pup PUP -6886?)* An external service (see also PUP-6867)* Algorithmical (PUP-6868) ** 6868 maybe be a dupe of this ticket ** similar to params.pp pattern*Note:* need an example of doing this with an existing module. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp for lookup static data
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6889 Expressing params.pp for lookup static data Change By: Eric Thompson As a module author currently using the params.pp pattern, I want to use a lookup data provider instead so that not all keys/values have to be computed even if not used so I can make my module perform better.Three key/value function types are supported for data that needs computation:* Data files that directly represents a data structure in json/yaml/hocon (interpolated) (pup-6886?) * An external service (see also PUP-6867)* Algorithmical (PUP-6868) ** 6868 maybe be a dupe of this ticket ** similar to params.pp pattern*Note:* need an example of doing this with an existing module. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp for lookup static data
Title: Message Title Eric Thompson commented on PUP-6889 Re: Expressing params.pp for lookup static data Henrik Lindberg how are we suggesting users migrate from params.pp to lookup? do you have an example given an existing module? interpolated data files seem to be covered in other tickets (using existing hiera files) this ticket may be about migrating params.pp which sounds like algorithm lookups where a function would be required (function would not be required in interpolated results, correct?) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp for lookup static data
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6889 Expressing params.pp for lookup static data Change By: Eric Thompson Summary: Expressing params.pp for lookup via functions static data Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6880) Initial migration from hiera v3 to v5
Title: Message Title Henrik Lindberg commented on PUP-6880 Re: Initial migration from hiera v3 to v5 Document where migration is discussed: https://docs.google.com/document/d/12bX5iq-RD6iQ9Ipd5yTEbg2jzezYKGjVJBUu-yKuGgs/edit#heading=h.xwi6nh2kcts3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp for lookup via functions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6889 Expressing params.pp for lookup via functions Change By: Eric Thompson As a module author currently using the params.pp pattern, I want to use a lookup data provider instead so that not all keys/values have to be computed even if not used so I can make my module perform better.Three key/value function types are supported for data that needs computation:* Data files that directly represents a data structure in json/yaml/hocon (interpolated) * An external service (see also PUP-6867)* Algorithmical (PUP-6868) ** similar to params.pp pattern *Note:* need an example of doing this with an existing module. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp for lookup via functions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6889 Expressing params.pp for lookup via functions Change By: Eric Thompson Summary: Expressing params.pp as for lookup static data via functions Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6880) Initial migration from hiera v3 to v5
Title: Message Title Henrik Lindberg commented on PUP-6880 Re: Initial migration from hiera v3 to v5 This is being discussed atm. I have written a proposal. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6884) class parameter default data-syntax and usage for module authors
Title: Message Title Henrik Lindberg commented on PUP-6884 Re: class parameter default data-syntax and usage for module authors Not sure what you mean by "defaults.pp" - is that params.pp pattern? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6889) Expressing params.pp as lookup static data
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6889 Expressing params.pp as lookup static data Change By: Eric Thompson As a module author currently using the params.pp pattern, I want to use a lookup data provider instead so that not all keys/values have to be computed even if not used so I can make my module perform better.Three key/value function types are supported for data that needs computation:* Data files that directly represents a data structure in json/yaml/hocon* An external service (see also PUP-6867)* Algorithmical (PUP = - 6868)*Note:* need an example of doing this with an existing module. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6880) Initial migration from hiera v3 to v5
Title: Message Title Eric Thompson commented on PUP-6880 Re: Initial migration from hiera v3 to v5 Henrik Lindberg do we know what direction we're going with regards to a mixture across environments of classical hiera (possibly global) and lookup v5? will we support different types of lookup this way across modules? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6880) Initial migration from hiera v3 to v5
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6880 Initial migration from hiera v3 to v5 Change By: Eric Thompson Acceptance Criteria: * see related acceptance ticket: use lookup.conf to get data from classical/existing hiera data files* a mix of classic hiera in one environment and v5 lookup in another should merge correctly Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6884) class parameter default data-syntax and usage for module authors
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6884 class parameter default data-syntax and usage for module authors Henrik Lindberg can you confirm/deny this is the correct acceptance criteria w.r.t what should be tested here? Change By: Eric Thompson Acceptance Criteria: * ensure existing tests cover description.** if no defaults.pp: ** a class parameter default value(s) come from lookup data ** same value as would have happened with hiera As a module author, I want to specify class parameter defaults so that consumers of my module only have to override the parameters that they need to be different.*Note:* my assumption is that this ticket is about the validation and documentation for class parameter default values because the implementation is covered elsewhere. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you
Jira (PUP-6886) Compatibility with hiera 3 JSON/YAML files
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6886 Compatibility with hiera 3 JSON/YAML files Change By: Eric Thompson Acceptance Criteria: * same results from lookup as with classic hiera without modifying hiera data files ** existing acceptance should do this, confirm: ** global vs. environment vs. module with classic hiera data, works Summary: Compatibility with hiera 3 JSON /YAML files As a hiera v3 user with YAML and JSON data files, I want to get the same results from lookup as I do witih classic hiera without modifying my JSON hiera data files so that I can begin adopting lookup without having to worry about modifying my hiera data first. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title Corey Osman commented on PUP-4800 Re: Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly A regex example is also here: http://rubular.com/r/wCSGrtZmhI Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title
Corey Osman updated an issue
Puppet / PUP-4800
Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Change By:
Corey Osman
I was creating a windows provider that consumed a ini file. I decided that I would use the Puppet::Util::IniConfig::PhysicalFile to parse my ini file however it seems one of the regex values is not able to parse my content.# regex that has trouble with my ini contenthttps://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/inifile.rb#L151The content that breaks this is found here and I have highlighted the line where it breaks: https://gist.github.com/logicminds/1d4bea2d5ac0285e3417#file-gistfile1-txt-L34At a glance I think just using the split function to capture the right and left side of the equal sign would work, but I am sure its more complicated than that as I don't have any other inclination of what goes into an ini file.My provider code does something like this for reference and was hoping to utilize the work of the utility rather than reinventing the wheel. {code:ruby} inffile = 'c:\\windows\\temp\\secedit.inf' secedit(['/export', '/cfg', inffile, '/quiet'])inf = Puppet::Util::IniConfig::PhysicalFile.new(inffile).read {code} So the regex can't handle the awesomeness of windows files and I assume this affects all versions of puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title Corey Osman updated an issue Puppet / PUP-4800 Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly Change By: Corey Osman I was creating a windows provider that consumed a ini file. I decided that I would use the Puppet::Util::IniConfig::PhysicalFile to parse my ini file however it seems one of the regex values is not able to parse my content.# regex that has trouble with my ini contenthttps://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/inifile.rb#L151The content that breaks this is found here and I have highlighted the line where it breaks: https://gist.github.com/logicminds/1d4bea2d5ac0285e3417#file-gistfile1-txt-L34At a glance I think just using the split function to capture the right and left side of the equal sign would work, but I am sure its more complicated than that as I don't have any other inclination of what goes into an ini file.My provider code does something like this for reference and was hoping to utilize the work of the utility rather than reinventing the wheel. inffile = 'c:\\windows\\temp\\secedit.inf' secedit(['/export', '/cfg', inffile, '/quiet'])inf = Puppet::Util::IniConfig::PhysicalFile.new(inffile).readSo the regex can't handle the awesomeness of windows files and I assume this affects all versions of puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Henrik Lindberg commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error Is there a stack trace for this error? It would be helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6929) Improvements around hiera error messaging
Title: Message Title Henrik Lindberg commented on PUP-6929 Re: Improvements around hiera error messaging Erik Hansen Sorry to be a pain here... but: Issues in Hiera are a plenty and we have therefore for quite some time been moving away to lookup. We are only fixing major bugs in Hiera (as it is a brittle implementation and much of the code is duplicated in plugins made by users and impossible to fix/change) This ticket should be for hiera as the problems described occur inside hiera code, or in plugins to hiera (at the same time we are probably not going to change this in hiera). In general - The problems that arise from faulty data files (bad yaml, unintentional faulty structure in data etc) can lead to any kind of error later - in older code especially troublesome since there was almost no type checking - thus leading to something like messages being sent to nil (where a nil was never expected). That meant the error occurred even further away from where the actual mistake was made. With lookup the same problems will be there - we cannot know if it is ok to return an array or hash, or what the content is supposed to be unless there is enough type information put in by users! We can make sure that the lookup implementation is doing its best to raise meaningful errors - but many are just impossible to say something intelligent about. One thing we have done in lookup is to minimize the amount of code an implementor of a backend has to write - thus making it more our responsibility to handle errors in a good way. In general, a "hiera data linter" is a tool that would be very helpful to a lot of users, but one does not really exists. The only thing I am aware of is puppet-syntax which at least checks that yaml and json files are syntactically correct. Users can greatly improve the quality of their code by using Puppet 4 and typing their parameters in classes and defines, and by using lookup and typing the expected result. They will then get immediate errors for bad data at a point where it makes sense. For lookup we will be happy to fix any bad error messages that does not fall in the general category of "user intended something else" as those will continue to be problematic. However, when users have made mistakes, there is "lookup --explain" that should provide information about how a key gets resolved. It should provide insights into what may be wrong so a user can more easily pin point where the problem is. And finally, and what you probably will like the least after having taken the time to write the ticket - I am afraid that It is not really possible to act on the error messages alone as posted in the description of this ticket. To make them actionable, it would be great to get a reproducible example(s) using lookup as opposed to hiera (i.e. with data inside of an env) - one ticket each. Also, ping Lindsey Smith as to the importance of tooling to assert data quality. I am closing this ticket as I don't see how we can act on it.
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6759
systemd provider does not understand "indirect" status / tries to turn off service on each run
Change By:
William Hopper
Acceptance Criteria:
The {{rpcbind}} service on RedHat 7 should show up as {{enabled => false}} when puppet is run with {{puppet resource service rpcbind}}.
Labels:
maintenance provider systemd
Story Points:
1
Release Notes Summary:
The systemd provider now considers services with the 'indirect' enabled state to be disabled.
Team:
Agent & Platform Puppet Developer Support
Sprint:
PDS 2016-11-30
Release Notes:
Bug Fix
Add Comment
Jira (PUP-6931) Scheduled_task only recognizes "xp" type tasks
Title: Message Title Mike Smith created an issue Puppet / PUP-6931 Scheduled_task only recognizes "xp" type tasks Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-11-17 at 12.33.48 PM.png Created: 2016/11/17 12:34 PM Priority: Normal Reporter: Mike Smith In testing an issue with mcollective scheduled tasks on a 2012r2 node, we noticed that the tasks are created as 2000/xp types. Changing a task to a newer type resulted in "puppet resource schedule_task" not finding the existing scheduled tasks. Add Comment
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: William Hopper Assignee: Kylo Ginsberg William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6930) Disallow multiple case and selector expression defaults
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6930 Disallow multiple case and selector _expression_ defaults We cannot change this and stay backwards compatible as it may break otherwise fully functional code. What we need to do is to make it always warn, and if strict=error issue an error. We also need a ticket for Puppet 5.0.0 where it is made into always error on duplicate literal default entries. Change By: Henrik Lindberg Acceptance Criteria: That multiple selector or case _expression_ literal defaults always generates a warning, and if strict=error raises an error. Story Points: 1 Release Notes Summary: It was possible to specify more than one literal default in a selector or case _expression_. Now this will always generate a warning unless strict=error. In a later release this will lead to an error. Team: Puppet Developer Support Summary: Disallow multiple case and selector _expression_ defaults . Sprint: PDS Triage Release Notes: Bug Fix Fix Version/s:
Jira (PUP-6930) Disallow multiple case defaults.
Title: Message Title Henrik Lindberg commented on PUP-6930 Re: Disallow multiple case defaults. The same problem exists for Case expressions as for Selectors. Code look like this on master (to be 4.9.0) in checker_4_0.rb: def check_CaseExpression(o) rvalue(o.test) # There should only be one LiteralDefault case option value # TODO: Implement this check end And for selector there is not even a TODO: def check_SelectorExpression(o) rvalue(o.left_expr) end
Jira (PUP-6921) Improve separation of concern between String and Enum types
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6921 Improve separation of concern between String and Enum types Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run Robert Rosengren my understanding of the indirect status (as detailed in https://www.freedesktop.org/software/systemd/man/systemctl.html) is that we should simply return false for is_enabled? when we come across such a service. Does that sound correct to you? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6821) binary_file() file not found: error message unclear
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6821 binary_file() file not found: error message unclear Change By: Henrik Lindberg Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6821) binary_file() file not found: error message unclear
Title: Message Title Henrik Lindberg commented on PUP-6821 Re: binary_file() file not found: error message unclear merged to master at: 25831ee Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) (SPIKE) Find a workflow for POT file generation
Title: Message Title Moses Mendoza commented on PUP-6761 Re: (SPIKE) Find a workflow for POT file generation I think an email to discuss-agent-and-platform@ makes sense, + confluence Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) (SPIKE) Find a workflow for POT file generation
Title: Message Title Maggie Dreyer commented on PUP-6761 Re: (SPIKE) Find a workflow for POT file generation Thanks for the input everyone! Do we want to see this go out as an email, and if so, to which lists? Alternatively/in addition, maybe a confluence doc? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) (SPIKE) Find a workflow for POT file generation
Title: Message Title Moses Mendoza assigned an issue to Maggie Dreyer Puppet / PUP-6761 (SPIKE) Find a workflow for POT file generation Change By: Moses Mendoza Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) (SPIKE) Find a workflow for POT file generation
Title: Message Title Moses Mendoza commented on PUP-6761 Re: (SPIKE) Find a workflow for POT file generation Made a couple minor clarifying suggestions in the doc but otherwise looks good to me Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) (SPIKE) Find a workflow for POT file generation
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-6761 (SPIKE) Find a workflow for POT file generation Change By: Moses Mendoza Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3196) (maint) pin addressable gem to avoid ruby 2 dependency
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3196 (maint) pin addressable gem to avoid ruby 2 dependency Issue Type: Bug Assignee: Unassigned Created: 2016/11/17 11:17 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (FACT-1536) Add top-level facts to output from `--list-X-groups` commands
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Maggie Dreyer Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1536) Add top-level facts to output from `--list-X-groups` commands
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Maggie Dreyer Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1536) Add top-level facts to output from `--list-X-groups` commands
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3195) Reset (nothing) on connection org.postgresql.jdbc.PGconnection@5ca523a
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3195 Reset (nothing) on connection org.postgresql.jdbc.PGconnection@5ca523a Issue Type: Improvement Assignee: Unassigned Created: 2016/11/17 11:07 AM Priority: Normal Reporter: Wyatt Alt I'm looking through some user logs. At the DEBUG level they contain this lines several times a second, and often 20-30 times/sec 2016-11-03 00:00:02,431 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6ca024b 2016-11-03 00:00:02,433 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6f86217a 2016-11-03 00:00:02,440 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6ca024b 2016-11-03 00:00:02,444 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6f86217a
Jira (PUP-6920) Windows package provider should set working directory (cwd)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6920 Windows package provider should set working directory (cwd) Change By: Geoff Nichols Sprint: AP Triage Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6919) Puppet::Util::Windows::Process.execute should accept a working directory
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6919 Puppet::Util::Windows::Process.execute should accept a working directory Change By: Geoff Nichols Sprint: AP Triage Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6918) SSL - Improve CSR to local public key mismatch handling
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6918 SSL - Improve CSR to local public key mismatch handling Change By: Geoff Nichols Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6918) SSL - Improve CSR to local public key mismatch handling
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6918 SSL - Improve CSR to local public key mismatch handling Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6918) SSL - Improve CSR to local public key mismatch handling
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6918 SSL - Improve CSR to local public key mismatch handling Change By: Geoff Nichols Labels: maintenance ssl Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6914) ruby expand_path in file type breaks leading-tilde file resources
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6914 ruby expand_path in file type breaks leading-tilde file resources Change By: Geoff Nichols Sprint: AP Triage Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1534) Acceptance: Facter seg faults on Cisco XR during default file location test
Title: Message Title Stan Duffy commented on FACT-1534 Re: Acceptance: Facter seg faults on Cisco XR during default file location test Michael Smith No, this test failed the last time we ran it too, it just wasn't ticketed from what I can tell. Last run was against facter 3.5.0-33-g01c09a2. This test has passed before on facter 3.5.0-30-g6b2a4f2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6909) useradd provider fails if the current value of user's expiry is nil
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6909 useradd provider fails if the current value of user's expiry is nil Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6906) ensure => absent and recurse => true with a source results in error
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6906 ensure => absent and recurse => true with a source results in error Change By: Geoff Nichols Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6906) ensure => absent and recurse => true with a source results in error
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6906 ensure => absent and recurse => true with a source results in error Change By: Geoff Nichols Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6906) ensure => absent and recurse => true with a source results in error
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6906 ensure => absent and recurse => true with a source results in error Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4800 Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly Change By: Geoff Nichols Labels: needs_repro windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4800 Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6930) Disallow multiple case defaults.
Title: Message Title Hunter Haugen created an issue Puppet / PUP-6930 Disallow multiple case defaults. Issue Type: Bug Assignee: Unassigned Components: Language Created: 2016/11/17 9:55 AM Priority: Normal Reporter: Hunter Haugen Apparently multiple default blocks are possible: https://github.com/puppetlabs/puppetlabs-postgresql/pull/798 Add Comment This message was sent by Atlassian JIRA
Jira (PUP-6927) Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename
Title: Message Title Colin Conway commented on PUP-6927 Re: Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename Thanks Moses Mendoza, I can't believe I didn't think of that. I'll try moving the files to the puppet server itself, and see if that fixes it. I'll let you know the outcome. bear with me though, I won't be able to test it until Monday. Thanks =) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6927) Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename
Title: Message Title
Moses Mendoza commented on PUP-6927
Re: Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename
Colin Conway it's not the most faithful reproduction but I didn't have any trouble on windows server 2012 r2 just doing a basic copy of a file with a tilde in the name:
C:\Users\moses\development\puppet(pr/5354)> be puppet apply -e " file { 'C:\Users\moses\dest\filewith~tilde' : ensure => present, source => 'C:\Users\moses\foo\filewith~tilde' } "
Notice: Compiled catalog for win-ghb4gdkiluo.localdomain in environment production in 0.07 seconds
Notice: /Stage[main]/Main/File[C:\Users\moses\dest\filewith~tilde]/ensure: defined content as '{md5}1d4ff57be8c328e117a34fa72fcd7c8d'
Notice: Applied catalog in 0.09 seconds
That error it mentions: " The process cannot access the file because it is being used by another process. " makes me wonder if it does have something to do with the file system / cifs mount
Add Comment
Jira (PUP-6927) Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename
Title: Message Title Moses Mendoza commented on PUP-6927 Re: Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename I wonder if this is related to PUP-6914 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6922) Types that ruby require other types can cause failure
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6922 Types that ruby require other types can cause failure Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3194) fix processed endpoint typo
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3194 fix processed endpoint typo Issue Type: Bug Assignee: Unassigned Created: 2016/11/17 8:00 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6861) [regression] Mount options not idempotent
Title: Message Title
Daniel Klockenkämper commented on PUP-6861
Re: [regression] Mount options not idempotent
Also affected: Gentoo, no systemd, puppet-agent 1.8.0 when having samba or nfs mounts in place
Example puppet options:
options => "credentials=/etc/samba/fstab_credentials,rw,uid=${samba_owner},gid=${samba_owner},forceuid,file_mode=${samba_mode},dir_mode=${samba_mode},nobrl,iocharset=utf8,_netdev,auto,noserverino,cache=loose,noacl,vers=3.0,echo_interval=60"
/etc/fstab:
credentials=/etc/samba/fstab_credentials,rw,uid=www-data,gid=www-data,forceuid,file_mode=0777,dir_mode=0777,nobrl,iocharset=utf8,_netdev,auto,noserverino,cache=loose,noacl,vers=3.0,nobootwait,nofail
/proc/self/mounts / /etc/mtab:
rw,relatime,vers=3.0,sec=ntlmssp,cache=loose,username=***,domain=***,uid=81,forceuid,gid=81,forcegid,addr=***,file_mode=0777,dir_mode=0777,iocharset=utf8,nounix,mapposix,nobrl,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1
Add Comment
Jira (PUP-6922) Types that ruby require other types can cause failure
Title: Message Title Craig Dunn commented on PUP-6922 Re: Types that ruby require other types can cause failure Henrik Lindberg Thomas Hallgren thanks for the input, i've done some very preliminary testing using Puppet::Type.type(:foo) and it does appear to work for me, at least for my use case. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6861) [regression] Mount options not idempotent
Title: Message Title Steph Gosling commented on PUP-6861 Re: [regression] Mount options not idempotent Late to the party it appears but also affects Ubuntu 12.04 with puppet-agent 1.8.0-1precise but not 12.04 with 1.5.2-1precise Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg commented on PUP-4742 Re: Bring semantic_puppet library into Puppet I was referring to the linked comment about "semantic-puppet 0.1.2" being included in the agent. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6922) Types that ruby require other types can cause failure
Title: Message Title Henrik Lindberg commented on PUP-6922 Re: Types that ruby require other types can cause failure Craig Dunn While that works now, it is based on knowledge about the current implementation; that the type's implementation is a Ruby class tied to a particular constant. That will eventually not be true and there is no way to help that code do the right thing in the future. The call Thomas showed is API and will continue to work (or gracefully be changed to something else). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6924) Fix issues with bad separation of concern between Array, Hash and Collection types
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6924 Fix issues with bad separation of concern between Array, Hash and Collection types Change By: Henrik Lindberg Fix Version/s: PUP 4.8.z Fix Version/s: PUP 4.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6924) Fix issues with bad separation of concern between Array, Hash and Collection types
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6924 Fix issues with bad separation of concern between Array, Hash and Collection types Change By: Henrik Lindberg Release Notes Summary: no user visible change Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6924) Fix issues with bad separation of concern between Array, Hash and Collection types
Title: Message Title Henrik Lindberg commented on PUP-6924 Re: Fix issues with bad separation of concern between Array, Hash and Collection types merged at c7450bb Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6924) Fix issues with bad separation of concern between Array, Hash and Collection types
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6924 Fix issues with bad separation of concern between Array, Hash and Collection types Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6922) Types that ruby require other types can cause failure
Title: Message Title Craig Dunn commented on PUP-6922 Re: Types that ruby require other types can cause failure Thanks Thomas Hallgren The (potential) problem with this is that under certain circumstances, I think when the puppet master is not pluginsynced or in certain puppet apply scenarios that Puppet can't find the type unless it's specifically references with it's fully qualified path, this was the reason for basing the require on _FILE_ in the first place after this was spotted in https://github.com/crayfishx/puppet-firewalld/issues/78 That issue is quite old and on Puppet 3 and i'll need to verify that we won't re-introduce that issue... I'll test your suggestion in a variety of scenarios and see if it does what we need. In the meantime, a quick work around for the above I came up with was: require File.join(File.dirname(__FILE__),'test_one') unless defined?(Puppet::Type::Test_one) That appears to pass without error. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-6922) Types that ruby require other types can cause failure
Title: Message Title Thomas Hallgren commented on PUP-6922 Re: Types that ruby require other types can cause failure A debug trace reveals the following. Broken scenario: 'include tesmodule::broken' is called. the type 'test_one' is autoloaded the type 'test_two' is autoloaded the code in 'test_two' creates the 'test_one' type again. This fails. Working scenario: 'include tesmodule::working' is called. the type 'test_two' is autoloaded the code in 'test_two' creates the 'test_one' type. This succeeds. no autoload of 'test_one' takes place since it's already loaded. I think Puppet does what it is supposed to do. It's not OK to create a type during autoload of another type. Doing so has probably always instantiated two Ruby types in memory but earlier (before the 4x loaders where involved) this went undetected. The correct way to do this is to reference the type instead of forcefully creating it using a require. it. I.e. replace this: require File.join(File.dirname(__FILE__),'test_one') with this: Puppet::Type.type(:test_one)
Jira (PUP-6922) Types that ruby require other types can cause failure
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6922 Types that ruby require other types can cause failure Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6921) Improve separation of concern between String and Enum types
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6921 Improve separation of concern between String and Enum types Change By: Thomas Hallgren Assignee: Thomas Hallgren Sprint: PDS 2016-11-30 Fix Version/s: PUP 4.8.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6861) [regression] Mount options not idempotent
Title: Message Title Stig Sandbeck Mathisen commented on PUP-6861 Re: [regression] Mount options not idempotent In Debian, /etc/mtab was made a symlink to /proc/mounts in the "wheezy" release in 2013. https://www.debian.org/releases/wheezy/amd64/release-notes/ch-information.en.html#mtab It does not look related to systemd. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
