Jira (PUP-6571) An invalid path to the --logdest option is silently ignored
Title: Message Title Josh Cooper commented on PUP-6571 Re: An invalid path to the --logdest option is silently ignored Should puppet log an error to the console and exit non-zero? I think right now puppet only cares that an absolute path is specified, but it doesn't check if the parent directories exist. 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-6989) Acceptance testing using TYPE=git and preserved hosts is broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6989 Acceptance testing using TYPE=git and preserved hosts is broken Change By: Josh Cooper Story Points: 3 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-7000) PMT should remind user to pluginsync
Title: Message Title Josh Cooper commented on PUP-7000 Re: PMT should remind user to pluginsync Ideally, the compiler should only be using the type information from the environment that the agent is in. So if you puppet module install and use code mgr to deploy, I would expect the environment isolation work to load the new types immediately. Relying on pluginsync to download the types (for whatever environment the master is in) into the agent's libdir so that it's visible to the master is not a good workflow. /cc Eric Sorenson 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-1434) Disallow manifests from declaring things outside the namespace implied by their filenames
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-1434
Disallow manifests from declaring things outside the namespace implied by their filenames
Change By:
Eric Sorenson
This ticket captures and elaborates on a decision made on the developer mailing list in late September 2014 (see email thread "PL RFC-1: Semantics of autoloaded classes").The contents of autoloaded .pp files should be restricted as follows:1. All classes defined in the file must have a name that matches the filename, or is nested within the namespace implied by the filename. So, for example, a file foo.pp can contain classes called "foo", "foo::bar", "foo::bar::baz", or "foo::baz", but not "bar".2. In files that are in subfolders, the portions of the path are joined by "::" to determine what classes are allowed. So, for example, a file foo/bar.pp can contain classes called "foo::bar" or "foo::bar::baz", but not "foo" or "foo::baz". Exception: class foo is allowed for the sole purpose of nesting (this allows constructions like{code:puppet}class foo { class bar { ... } }").{code}3. Defines follow similar rules4. No toplevel constructs (resources, variable assignments, include statements, import statements, etc) are allowed in autoloaded modules.5. In files that are autoloaded from modules, the module name is included in the path, but the subdirectory "manifests" is not. So for example, the file {{$module_path/foo/manifests/bar.pp}} follows the same rules as {{ foo/bar.pp}}.6. In a module's {{init.pp}} file, "init" is not included in the path. So for example, the file {{$module_path/foo/manifests/init.pp}} follows the same rules as {{foo.pp}}.7. Everything that is loaded from the enviroment is allowed to use any namespace. (This is also the exploratory mode when writing example snippets).Because of the pervasive nature of this change, we plan to implement a deprecation warning in one release, to warn users of the impending change, and defer the actual change to a later release. This ticket is for the actual change. PUP-4242 is the deprecation warning ticket.
Add Comment
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-893 Deprecate puppet inspect and the audit metaparameter Change By: Eric Sorenson Fix Version/s: PUP 4.y Fix Version/s: PUP 5.0.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-6504) Targeted Filebucket Improvements
Title: Message Title Eric Sorenson commented on PUP-6504 Re: Targeted Filebucket Improvements Moses Mendoza maybe just the bits that need to be on the major version - looks like the settings change in PUP-5206 and the face deprecation/removal PUP-869... pretty low priority IMO 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-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Eric Thompson commented on PUP-6992 Re: Fix inconsistent autoload of environment functions and pcore types. okay. and the assumption is more or less that the loader replaces the / on filesystem, with :: in function name when finding/loading functions? so they can't all just be in $environment/functions or $environment/lib/puppet/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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Eric Sorenson commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module FWIW the only part of this proposal I have heard users ask for is marking classes private, so they do not show up for assignment in the console classifier and are not enumerated with the environment_classes endpoint. 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Eric Sorenson commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module (Non-Trevor users, I mean) 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-6951) No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted”
Title: Message Title Eric Sorenson commented on PUP-6951 Re: No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted” Jens Offenbach 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-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Henrik Lindberg commented on PUP-6992 Re: Fix inconsistent autoload of environment functions and pcore types. You want to have the ability to name the functions environment::blah() in order to prevent the function you are writing to not clash with functions that are in no namespace (global) for example blah(). You don't want to name the function after the name of the environment as it changes depending on where it is checked out, so production::blah() does not make sense. 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Henrik Lindberg commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Yes, maybe You can set parameters in data files inside the module (hiera version 4 and 5). There could be a distinction made for private such that those data values are not allowed to be overridden by data in the environment or global layers. This would make sense if private means "private to the implementation" and therefore "private to the module author". You could still, in the same module, override those by giving value explicitly. No other module would be able to do either one of those. We could naturally take a more relaxed approach allowing values to be bound in any layer even if the class is private - thereby being closer to the notion of protected. You may want to use class parameters because you want hierarchical data resolution using APL at the same time as you do not want anyone to mess with the values. 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-4555) Iterate on Directory Environments
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4555 Iterate on Directory Environments Change By: Eric Sorenson Epic Status: To Do Done 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Trevor Vaughan commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Henrik Lindberg I was thinking more about this and I don't know that I see the point of a class where I can't set the parameters via data binding. If I don't want someone to mess about with the variables in my class, I just don't make them parameters. Am I missing something? 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-3211) Collect/expose metrics on vacuum stats
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3211 Collect/expose metrics on vacuum stats Change By: Karen Van der Veer Sprint: Hopper SE 2016-01-11 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-7000) PMT should remind user to pluginsync
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-7000
PMT should remind user to pluginsync
Change By:
Ben Ford
When the user installs a module with ` {{ puppet module install ` }} and types are installed/updated, it should print a warning out that pluginsync should be run on the master before it can be used.
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-7001) CodeManager should remind user to pluginsync
Title: Message Title Ben Ford created an issue Puppet / PUP-7001 CodeManager should remind user to pluginsync Issue Type: Bug Assignee: Unassigned Created: 2016/12/12 3:13 PM Priority: Normal Reporter: Ben Ford When the user installs a module with `puppet module install` and types are installed/updated, it should print a warning out that pluginsync should be run on the master before it can be used. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7000) PMT should remind user to pluginsync
Title: Message Title Ben Ford created an issue Puppet / PUP-7000 PMT should remind user to pluginsync Issue Type: Bug Assignee: Unassigned Created: 2016/12/12 3:12 PM Priority: Normal Reporter: Ben Ford When the user installs a module with `puppet module install` and types are installed/updated, it should print a warning out that pluginsync should be run on the master before it can be used. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Michael Smith updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Michael Smith Labels: davis-ss maintenance pe 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-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Eric Thompson commented on PUP-6992 Re: Fix inconsistent autoload of environment functions and pcore types. thanks, that makes sense Henrik Lindberg. Thomas Hallgren if that's the case. why would we need functions named environment::blah and why would they be isolated into: /lib/puppet/functions/environment # ruby /functions/environment # puppet i'm assuming here means "current environment's root" 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-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Henrik Lindberg commented on PUP-6992 Re: Fix inconsistent autoload of environment functions and pcore types. "global name" can only mean "top scoped name" here as there is no leakage between environments wrt. functions. A ::foo function in env A is different from a ::foo function in module B, and A and B cannot see into each-other. 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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Henrik Lindberg commented on PUP-6973 Re: Make Hiera v5 configuration sensitive to changes of interpolated values There are also $caller and $module_name which vary depending on where the call to hiera_xxx came from. Ping Thomas Hallgren for details. 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-6781) support 'verbatim' lookup option
Title: Message Title Henrik Lindberg commented on PUP-6781 Re: support 'verbatim' lookup option To not go crazy, think we should use the terms "lookup options" for what is in data and "data provider options" for the options per level in hiera.yaml. 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-6928) acceptance: hiera.yaml v5 with existing data files
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6928 acceptance: hiera.yaml v5 with existing data files Change By: Eric Thompson ensure we can use lookup hiera .yaml to enable lookups with existing data files. this will be named hiera.yaml in the near future. this test can be written before that name change is complete. later tests should be configuring global hiera lookups using hiera.yaml v5 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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Eric Thompson commented on PUP-6973 Re: Make Hiera v5 configuration sensitive to changes of interpolated values which scopes' variables does hiera.yaml have access to? i'm assuming it's just top scope. if so, this seems well covered by unit tests, even if we're talking about changes in a scope's membership/values. 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-6999) Revise Environments Limitations page re: env isolation
Title: Message Title Jean Bond created an issue Puppet / PUP-6999 Revise Environments Limitations page re: env isolation Issue Type: Bug Assignee: Jean Bond Components: DOCS Created: 2016/12/12 1:41 PM Priority: Normal Reporter: Jean Bond See last two comments in PUP-731 . This section: https://docs.puppet.com/puppet/latest/environments_limitations.html#plugins-running-on-the-puppet-master-are-weird should be revised to account for environment isolation as of Puppet 4.8 (or earlier? unclear to me) Add Comment
Jira (PUP-6781) support 'verbatim' lookup option
Title: Message Title Henrik Lindberg commented on PUP-6781 Re: support 'verbatim' lookup option Yes, you are right - I forgot. IIRC (ping Thomas Hallgren), the lookup function arguments wins over lookup_options (in data) which in turn wins over the level option. Not sure if there is a difference between the three functions - I think the default is "verbatim false" for data_hash, but "true" for the other two kinds of functions. Thomas Hallgren please correct me if I am wrong here. 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Jean Bond commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments I'm not going to lie, that's one of my favorite docs headings ever. Also, making a ticket for the docs work now, 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Henrik Lindberg commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Ping Jean Bond - see Jo Rhett's comment above. (This is "environment isolation"). 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-6781) support 'verbatim' lookup option
Title: Message Title Eric Thompson commented on PUP-6781 Re: support 'verbatim' lookup option Henrik Lindberg thanks for the context. in this case verbatim is set per level (in hiera.yaml): https://github.com/puppetlabs/puppet/pull/5421/files#diff-2c12cbb4931cfd2102db8d688e73049eR1073 can that be set per-key as you imply above using lookup_options? if so, what happens when they conflict? do we have or need testing around what happens with merged lookups across values and environments with different options? 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-6998) File attribute "target" forces file to be symlink if not already
Title: Message Title John Williamson updated an issue Puppet / PUP-6998 File attribute "target" forces file to be symlink if not already Change By: John Williamson Affects Version/s: PUP 3.8.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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Henrik Lindberg commented on PUP-6973 Re: Make Hiera v5 configuration sensitive to changes of interpolated values The difference in scopes given to hiera is of importance - that is where all the data interpolated in a hiera.yaml comes from. Hiera "classic" (a.k.a 3) recalculates all interpolations on each lookup, the hiera 4 implementation did not, and instead did all interpolations once (on first use) - thus making it insensitive to finding new/different values in the scope given on subsequent lookups. 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-6659) Information Disclosure - Puppet Server Stacktraces
Title: Message Title Susan McNerney commented on PUP-6659 Re: Information Disclosure - Puppet Server Stacktraces fyi, if there is a desire to get this into 2016.4.3, please create a new ticket and submit to the Davis Release and Z's hipchat channel. 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-6781) support 'verbatim' lookup option
Title: Message Title Henrik Lindberg commented on PUP-6781 Re: support 'verbatim' lookup option The lookup_options are set in data sources and its name is unchanged. The 'options:' in a hiera.yaml level entry is not the same as the lookup_options. The 'options:' in a level entry is for options to the function being called to produce data (things like a path, a URL, etc. depending on the type of function being used). The 'lookup_options' is for options per key in the data (for example if the value for a key is a deep merge, to be taken verbatim 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-6781) support 'verbatim' lookup option
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6781 support 'verbatim' lookup option this is covered well by unit tests. Henrik Lindberg, Thomas Hallgren we don't have great (any) coverage of the various places one can set lookup_options this can be set in the hiera.yaml file, covered by the unit tests here. can we still set this as a key in a data source? is the key still called lookup_options? what happens if we use options: in hiera.yaml and the same options in lookup_options key in a data source? Change By: Eric Thompson QA Risk Assessment Reason: covered well by unit tests QA Risk Assessment: No Action QA Contact: Eric Thompson Add Comment
Jira (PUP-1226) puppet breaking setuid bit on group change
Title: Message Title Stephen Gelman commented on PUP-1226 Re: puppet breaking setuid bit on group change We are running into the same issue under Debian. It seems to me like this is a legitimate bug that should be fixed. Leaving the permissions incorrect until the next puppet run does not seem to be an adequate solution. 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-6974) Looking up a 'false' value in hiera.yaml when using data in modules does not return a result.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6974 Looking up a 'false' value in hiera.yaml when using data in modules does not return a result. Change By: Eric Thompson QA Risk Assessment Reason: simple, rare use case. covered well by unit tests. QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Thompson 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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Eric Thompson commented on PUP-6973 Re: Make Hiera v5 configuration sensitive to changes of interpolated values this is well covered by unit tests. anyone have opinions on if we need acceptance tests? the mocking in the unit tests is basically just setting scope vars. i'm thinking that testing the interpolation functionality in hiera.yaml isn't important in this context. 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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6973 Make Hiera v5 configuration sensitive to changes of interpolated values Change By: Eric Thompson Acceptance Criteria: given: before all top scope variables are set when: lookupthen: should modify affected resolved interpolations (covered by unit tests, https://github.com/puppetlabs/puppet/pull/5410/files#diff-2c12cbb4931cfd2102db8d688e73049eR939) given: lookup made from a specific scope then: should see variables in scope (covered by unit tests) given: new scope/configurationwhen: lookupthen: debug output given (covered : before all top scope variables have been setwhen https : lookupthen: that needs to continue working //github . com/puppetlabs/puppet/pull/5410/files#diff-2c12cbb4931cfd2102db8d688e73049eR944) 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 (PDOC-153) There is no correct method for documenting class variables that are not parameters but are meant to be available.
Title: Message Title Trevor Vaughan commented on PDOC-153 Re: There is no correct method for documenting class variables that are not parameters but are meant to be available. As a quick note, I also realized that this issue applies to the $name parameter in Defined Types 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-6998) File attribute "target" forces file to be symlink if not already
Title: Message Title
John Williamson created an issue
Puppet / PUP-6998
File attribute "target" forces file to be symlink if not already
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/12/12 11:12 AM
Priority:
Trivial
Reporter:
John Williamson
It appears that no matter what the "ensure" attribute is set to, if the file being ensured is not a symlink and a "target" is specified, then puppet will ensure that it is a symlink.
As an example, say that you have a directory that needs to be a real directory on some systems and a symlink to another directory on other systems, you might make a hiera key $dir_ensure_val to contain what a server or group of servers will get, and then write the following puppet code:
file {"/this/is/my/directory": ensure => "$dir_ensure_val", target => "/usr/lib_global_directory"; }
If $dir_ensure_val is set to 'directory', then: --If /this/is/my/directory doesn't exist or is a symlink, this code will create /this/is/my/directory as a real, standard directory.
--If /this/is/my/directory is already a real directory, this code will attempt to replace /this/is/my/directory with a symlink that points to /usr/lib_global_directory
That means that if it's an empty directory, then puppet will alternate between the two indefinitely. If it's not an empty directory, then the code will succeed at creating the directory on the first run and fail on all subsequent runs because it can't delete the directory to replace it with a symlink.
This behavior should be consistent but isn't. Personally I'd love it if "target" was ignored if ensure isn't 'link' so that code with variable ensures can be used. However, if puppet were to always create a symlink if "target" is set, that also gives a consistent behavior.
Jira (PUP-6945) acceptance: lookup rich data values
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-6945 acceptance: lookup rich data values Change By: Eric Thompson Assignee: William Hopper Eric Thompson 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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6973 Make Hiera v5 configuration sensitive to changes of interpolated values Change By: Eric Thompson Acceptance Criteria: given: before all top scope variables are set when: lookupthen: should modify affected resolved interpolationsgiven: lookup made from a specific scope then: should see variables in scope given: new scope/configurationwhen: lookupthen: debug output given: before all top scope variables have been setwhen: lookupthen: that needs to continue working. 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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6973 Make Hiera v5 configuration sensitive to changes of interpolated values Change By: Eric Thompson Acceptance Criteria: given: before all top scope variables are set when: lookupthen: should modify affected resolved interpolationsgiven: lookup made from a specific scope then: should see variables in scope given: new scope/configurationwhen: lookupthen: debug output 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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6973 Make Hiera v5 configuration sensitive to changes of interpolated values Change By: Eric Thompson Acceptance Criteria: given: before all top scope variables are set when: lookupthen: should modify affected resolved interpolationsgiven: lookup made from a specific scope then: should see variables in scope 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-6942) Modify lookup to always use hiera.yaml.
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6942
Modify lookup to always use hiera.yaml.
Change By:
Eric Thompson
Release Notes Summary:
This change allows the use of {{hiera.yaml}} to configure data lookups in modules and environments in hiera v5. We also deprecate older uses and warn on conflicting configurations.
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-6942) Modify lookup to always use hiera.yaml.
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-6942 Modify lookup to always use hiera.yaml. Change By: Eric Thompson Assignee: qa 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-3226) PDB extensions should fail startup if any of the required databases don't exist
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3226 PDB extensions should fail startup if any of the required databases don't exist Issue Type: Improvement Assignee: Unassigned Created: 2016/12/12 10:59 AM Priority: Normal Reporter: Wyatt Alt Looks like it will fail today if the activity database is missing, but not if the rbac database is missing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6942) Modify lookup to always use hiera.yaml.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6942 Modify lookup to always use hiera.yaml. Change By: Eric Thompson Release Notes: New Feature 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-6942) Modify lookup to always use hiera.yaml.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6942 Modify lookup to always use hiera.yaml. Change By: Eric Thompson QA Risk Assessment Reason: warnings and deprecations; covered well by unit tests. hiera.yaml usage covered in acceptance elsewhere QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Thompson 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-6945) acceptance: lookup rich data values
Title: Message Title Eric Thompson assigned an issue to William Hopper Puppet / PUP-6945 acceptance: lookup rich data values Change By: Eric Thompson Assignee: Eric Thompson 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-6945) acceptance: lookup rich data values
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6945
acceptance: lookup rich data values
Change By:
Eric Thompson
Comment:
remove the colon from the hiera config{code}[root@idosxnpkpepttls some_mod]# puppet lookup --explain --environment lookup_rich_values_6xdoz5jm environment_keySearching for "lookup_options" Data Binding "hiera"No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/lookup_rich_values_6xdoz5jm/hiera.yaml"Hierarchy entry "Test"Syntax error at 'options' at /etc/puppetlabs/code/environments/lookup_rich_values_6xdoz5jm/modules/some_mod/functions/rich_data_test.pp:1:35 in Syntax error at 'options' at /etc/puppetlabs/code/environments/lookup_rich_values_6xdoz5jm/modules/some_mod/functions/rich_data_test.pp:1:35[root@idosxnpkpepttls lookup_rich_values_6xdoz5jm]# cat hiera.yaml---version: 5hierarchy: - name: Testdata_hash: "some_mod::rich_data_test"[root@idosxnpkpepttls lookup_rich_values_6xdoz5jm]# cat modules/some_mod/functions/rich_data_test.ppfunction some_mod::rich_data_test(options, context) { {"environment_key" => Sensitive('toe, no step'), }}{code}
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
Jira (PUP-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Jo Rhett commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Really should update https://docs.puppet.com/puppet/latest/environments_limitations.html to indicate which versions the big warning at the top applies to, now that this is fixed. 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-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title Kurt Wall commented on FACT-1539 Re: facter 3.5.0 (and 3.5.1) fail to build Sorry, I was unclear. I wasn't asking you to do the work, just if the added test was sufficient. If you thought it wasn't, I would have written an acceptance-level test. Given the overhead, though, it doesn't sound like the return would be high enough to justify the effort. It's an upstream bug anyway, it looks like, so there's little we could have done. 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-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title Kurt Wall updated an issue Facter / FACT-1539 facter 3.5.0 (and 3.5.1) fail to build Change By: Kurt Wall QA Risk Assessment: Needs Assessment No Action 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-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title Kurt Wall updated an issue Facter / FACT-1539 facter 3.5.0 (and 3.5.1) fail to build Change By: Kurt Wall QA Risk Assessment Reason: Upstream bug; high overhead to test 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 (PDOC-153) There is no correct method for documenting class variables that are not parameters but are meant to be available.
Title: Message Title
William Hopper updated an issue
Puppet Strings / PDOC-153
There is no correct method for documenting class variables that are not parameters but are meant to be available.
Change By:
William Hopper
Consider the following, commonly used, {{params.pp}}{ { code} } foo::params { $bar = 'baz'}{ { code} } In this case, I would like to be able to declare that the {{$foo::params::bar}} variable is available for use but it is not a {{parameter}}.Ideally, this would be documented with the {{@!accessor [r]}} method, but, when I attempted to use this, an error was thrown.Presently, I'll continue using {{@param}} but it is inherently incorrect and a more correct alternative should be supplied.
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 (PDOC-153) There is no correct method for documenting class variables that are not parameters but are meant to be available.
Title: Message Title
Trevor Vaughan created an issue
Puppet Strings / PDOC-153
There is no correct method for documenting class variables that are not parameters but are meant to be available.
Issue Type:
Bug
Affects Versions:
PDOC 1.0.0
Assignee:
Unassigned
Components:
DOCS
Created:
2016/12/12 10:11 AM
Priority:
Normal
Reporter:
Trevor Vaughan
Consider the following, commonly used, params.pp
code foo::params { $bar = 'baz' }
code
In this case, I would like to be able to declare that the $foo::params::bar variable is available for use but it is not a parameter.
Ideally, this would be documented with the @!accessor [r] method, but, when I attempted to use this, an error was thrown.
Presently, I'll continue using @param but it is inherently incorrect and a more correct alternative should be supplied.
Jira (FACT-1536) Add top-level facts to output from `--list-X-groups` commands
Title: Message Title Michael Smith commented on FACT-1536 Re: Add top-level facts to output from `--list-X-groups` commands I noticed in the demo... it could be nice to have a description at the top clarifying what's being shown. I'm not sure it's clear on its own. 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-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title Michael Smith commented on FACT-1539 Re: facter 3.5.0 (and 3.5.1) fail to build Covering this with testing would require building with several versions of GCC. I think it might've been an issue with GCC 4.9. That requires building several intermediate pieces, so I'd rather not put in the effort. 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 Kurt Wall updated an issue Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Kurt Wall QA Risk Assessment Reason: API change; visual check of output sufficient to validate 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 Kurt Wall updated an issue Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Kurt Wall QA Risk Assessment: Manual 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-1537) Facter 3.5.0 tarball is broken
Title: Message Title Kurt Wall updated an issue Facter / FACT-1537 Facter 3.5.0 tarball is broken Change By: Kurt Wall QA Risk Assessment Reason: Built Build failure 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-1537) Facter 3.5.0 tarball is broken
Title: Message Title Kurt Wall updated an issue Facter / FACT-1537 Facter 3.5.0 tarball is broken Change By: Kurt Wall QA Risk Assessment Reason: Built failure 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 (PDOC-150) README links broken after being HTMLfied
Title: Message Title David Hollinger III commented on PDOC-150 Re: README links broken after being HTMLfied That is definitely very similar, if not the same, issue I'm seeing with the README markdown not being properly parsed/processed into HTML. I can see if something is open with the redcarpet project if you haven't already created one 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-1537) Facter 3.5.0 tarball is broken
Title: Message Title Kurt Wall updated an issue Facter / FACT-1537 Facter 3.5.0 tarball is broken Change By: Kurt Wall QA Risk Assessment: No Action 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-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title Kurt Wall commented on FACT-1539 Re: facter 3.5.0 (and 3.5.1) fail to build Maggie Dreyer or Michael Smith Does the change to lib/tests/collection_fixture.hpp cover the automated testing needs for this bug? I can't evaluate the code because it's modern C++. 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-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Eric Thompson commented on PUP-6992 Re: Fix inconsistent autoload of environment functions and pcore types. For the sake of consistency, functions using global names should reside under: /lib/puppet/functions # ruby /functions # puppet does "global" imply that if i put a function as above, in one environment, it should be usable in another environment? what happens if there are two functions named the same thing in each environment? which one wins? what happens if there are two incompatible functions named the same thing, should the one in my environment be loaded if the other one was previously loaded? (environment isolation) 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-6925) Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding
Title: Message Title Kurt Wall updated an issue Puppet / PUP-6925 Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding Change By: Kurt Wall QA Risk Assessment Reason: [Bulk update] Testing, infrastructure, research tickets do not require risk assessment QA Risk Assessment: No Action 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-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6992 Fix inconsistent autoload of environment functions and pcore types. Change By: Eric Thompson When a *ruby* function is declared in a _func_name.rb_ file under the directory _/lib/puppet/functions_, the auto-loader makes it accessible using the global name "func_name". Declaring a *puppet* function in _func_name.pp_ under _/functions_ does , however , not work. The function is not found unless the name of the function is prefixed with "environment::". In contrast, if the *ruby* function is prefixed the same way, the function is no longer found unless it is also moved to _/lib/puppet/functions/environment_.For the sake of consistency, functions using global names should reside under:_/lib/puppet/functions_ # ruby_/functions_ # puppetand functions prefixed with "environment::" should reside under:_/lib/puppet/functions/environment_ # ruby_/functions/environment_ # puppetThe same scheme should be used for auto-loading pcore types that are declared in the environment (but beneath the _types_ directory instead of _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
Jira (PUP-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Kurt Wall updated an issue Puppet / PUP-6976 Scope effort to externalize Puppet report strings for translation Change By: Kurt Wall QA Risk Assessment Reason: [Bulk update] Testing, infrastructure, research tickets do not require risk assessment QA Risk Assessment: Needs Assessment No Action 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-6996) Puppet automatically creates the production environment with the incorrect permissions
Title: Message Title Adam Bottchen commented on PUP-6996 Re: Puppet automatically creates the production environment with the incorrect permissions https://github.com/puppetlabs/puppet/pull/5422 fixes this in my test environment. 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-6978) Distinguish errors in ClassInformationService response for class located in improper manifest file
Title: Message Title Jeremy Barlow commented on PUP-6978 Re: Distinguish errors in ClassInformationService response for class located in improper manifest file I don't have any recommendations for this ticket in terms of urgency. I tagged this as "Needs Priority" to see what the "CS" team thinks about this issue. 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-6978) Distinguish errors in ClassInformationService response for class located in improper manifest file
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6978 Distinguish errors in ClassInformationService response for class located in improper manifest file Change By: Jeremy Barlow CS Priority: Needs Priority 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-6978) Distinguish errors in ClassInformationService response for class located in improper manifest file
Title: Message Title Jeremy Barlow commented on PUP-6978 Re: Distinguish errors in ClassInformationService response for class located in improper manifest file Having the :error key next to the offending class would seem reasonable to me, assuming that maybe for space-saving purposes that we'd only need to include the key if one or more errors had been encountered. I'm also open to the approach of having a separate array with the names of the offending classes, if you'd prefer to go that way, so long as it will be feasible for the ultimate consumer of the info - e.g., the Node Classifier - to be able to clearly associate the error to the corresponding class without having to do any special manipulation of the payload. I also wanted to take a step back to make sure that the motivation for this ticket is clear. The user who encountered this problem had the same class name in two different manifests but with differing parameters in each. Using the mymodule::myclass example from the description again, let's say that the class was in the following manifests: /etc/puppetlabs/code/environments/production/modules/mymodule/manifests/myclass.pp /etc/puppetlabs/code/environments/production/modules/mymodule/manifests/somedir/myclass.pp Currently, Puppet Server will discover both of these manifests and ask the ClassInformationService to parse them. The ClassInformationService would return information for the mymodule::myclass in both manifests, along with the corresponding parameter information found for each. No indication of a problem with the duplication is included in the response payload today. If an include mymodule::myclass were to appear in the /etc/puppetlabs/code/environments/production/manifests/site.pp file, the class definition which would be used would, I believe, always be the one from the .../mymodule/manifests/myclass.pp and never the one from the .../mymodule/manifests/somedir/myclass.pp file. If one were to remove the .../mymodule/manifests/myclass.pp file, leaving the .../mymodule/manifests/somedir/myclass.pp file in place, I believe the include command would fail because the compiler would still not consider .../mymodule/manifests/somedir to be an appropriate location in which to find a class named mymodule::myclass. For the case that both of the classes with the same name were present in different manifests, I think it would be useful to have the ClassInformationService response continue to include information for both classes, per manifest in which the classes were found. If an error could be tagged onto the response for the class which exists at .../mymodule/manifests/somedir and the Node Classifier could then use that to prevent the parameters for the class definition which could not be used during an actual catalog compilation from being used in the classification UI, I think we'd satisfy the initial request which led to this ticket being created. It sounds good to me if we wanted to going further than this duplicate class definition case and tag errors for other cases - like where a class could be loaded but only if another class were defined and loaded first. But maybe it would be good to do that as a separate ticket depending upon how involved that may end up being.
Jira (PUP-6997) acceptance: can use pp functions located in ${environment}/functions
Title: Message Title
Eric Thompson created an issue
Puppet / PUP-6997
acceptance: can use pp functions located in ${environment}/functions
Issue Type:
Sub-task
Assignee:
Unassigned
Created:
2016/12/12 9:26 AM
Priority:
Normal
Reporter:
Eric Thompson
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
Jira (PUP-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6992 Fix inconsistent autoload of environment functions and pcore types. adding acceptance sub-task Change By: Eric Thompson QA Risk Assessment Reason: high risk, pp functions not loading in some cases QA Contact: Eric Thompson 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-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6992 Fix inconsistent autoload of environment functions and pcore types. Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate 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-6945) acceptance: lookup rich data values
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-6945 acceptance: lookup rich data values Change By: Eric Thompson Assignee: Eric Thompson 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Geoff Nichols assigned an issue to Sean McDonald Puppet / PUP-6777 regression: incompatible character encodings: UTF-8 and ASCII-8BIT Change By: Geoff Nichols Assignee: Sean McDonald 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-6996) Puppet automatically creates the production environment with the incorrect permissions
Title: Message Title Adam Bottchen created an issue Puppet / PUP-6996 Puppet automatically creates the production environment with the incorrect permissions Issue Type: Bug Affects Versions: PUP 4.8.1 Assignee: Unassigned Created: 2016/12/12 9:14 AM Priority: Normal Reporter: Adam Bottchen If the production environment does not exist, Puppet will automatically create it as a result of PUP-2519 . Unfortunately, it creates the directory with ownership of root:root. To be consistent with Code Manager and file sync, it should be owned by puppet user and group (pe-puppet:pe-puppet for PE installations). Add Comment
Jira (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Wyatt Alt commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration Susan McNerney Ryan Senior with AMQ out of the way in 2017.1 is this a noop? Is there still a fix to be made? 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-3225) Add Brian Cain as Maintainer
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3225 Add Brian Cain as Maintainer Issue Type: Bug Assignee: Unassigned Created: 2016/12/12 8:19 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 (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title
Brian Cain updated an issue
PuppetDB / PDB-3107
new-command-schema validation prevents PDB/NewRelic integration
Change By:
Brian Cain
This line:https://github.com/puppetlabs/puppetdb/blob/4.1.x/src/puppetlabs/puppetdb/command.clj#L169results in this error: ``` {noformat} 13:25 ```2016-10-13 23:05:30,557 ERROR [o.a.a.ActiveMQMessageConsumer] ID:ip-10-11-47-46.sj.b2c.nike.com-45556-1476399900148-6:1:1:1 Exception while processing messag13:25 e: ID:ip-10-11-47-46.sj.b2c.nike.com-45556-1476399900148-8:1:1:1:413:25 clojure.lang.ExceptionInfo: Input to parse-new-command does not match schema: [(named {:headers {:NewRelicID disallowed-key, :NewRelicTransaction disallowed-13:25 key, :JMSXDeliveryCount disallowed-key}} arg0)]``` ``` {noformat} when PDB is run with the newrelic agent (supplied via java args). Instead of nailing down the exact schema we should just require the appropriate minimal set of keys/headers.
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-3224) Add the ability to stop processing different types of commands via API
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API Change By: Nick Walker h1. The Use CaseI'd like to REBUILD some indexes or VACUUM FULL a table but when I do the PuppetDB service continues trying to write changes to the table. I'd like to run PuppetDB GC via the api and when I do, stop processing the type of command I'm cleaning up to reduce contention on the database. h1. ThoughtsI think the GC case is an added benefit but probably not enough of a win to warrant this feature. The real benefit comes from being able to allow database maintenance while the service stays up and queues the incoming commands. If I don't process facts while I'm performing a blocking operation on one of the facts tables that means that I can still keep my commands / sec up by processing reports instead of lowering my throughput with lots of failed commands on facts. This means I keep the queue lower overall during a maintenance period. 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-3224) Add the ability to stop processing different types of commands via API
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API Issue Type: New Feature Assignee: Unassigned Created: 2016/12/12 8:07 AM Labels: tcse Priority: Normal Reporter: Nick Walker The Use Case I'd like to REBUILD some indexes or VACUUM FULL a table but when I do the PuppetDB service continues trying to write changes to the table. I'd like to run PuppetDB GC via the api and when I do, stop processing the type of command I'm cleaning up to reduce contention on the database. Thoughts I think the GC case is an added benefit but probably not enough of a win to warrant this feature. The real benefit comes from being able to allow database maintenance while the service stays up and queues the incoming commands. Add Comment
Jira (PDOC-152) Strings should support the documentation of private classes
Title: Message Title Henrik Lindberg commented on PDOC-152 Re: Strings should support the documentation of private classes marked as blocked by PUP-523 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Henrik Lindberg commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module In PDOC-152, Trevor Vaughan brings up that it is meaningful to differentiate between private and protected classes as it is meaningful to be able to set parameters via APL for those that are protected. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Erik Hansen commented on PUP-6986 Re: Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Anyone hitting this issue might be able to work around the problem by setting the environment variable LC_CTYPE=en_US.UTF-8 either as a system setting or applied to the environment that the agent runs in. 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 (PDOC-152) Strings should support the documentation of private classes
Title: Message Title Henrik Lindberg commented on PDOC-152 Re: Strings should support the documentation of private classes We should have this discussion in PUP-523 as this ticket (PDOC-152) is about how the outcome of that ticket would look like when documented. 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 (PDOC-152) Strings should support the documentation of private classes
Title: Message Title Trevor Vaughan commented on PDOC-152 Re: Strings should support the documentation of private classes Henrik Lindberg Yes, this is exactly what I would need. I would expect my data bindings to work on protected classes but not private classes. Also, probably 99% of my classes (and probably everyone else's) would be protected because nobody wants to do the work to make sure that all parameters are exposed everywhere, nor do we want to deconflict the thing parameter from 4 different subclasses. That way lies reverting to the madness of params.pp. 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 (PDOC-152) Strings should support the documentation of private classes
Title: Message Title Henrik Lindberg commented on PDOC-152 Re: Strings should support the documentation of private classes What would protected mean? I am guessing that you cannot include them (unless from within the module), but you can set parameters via APL ? The semantics for private has not been determined yet (we only have the keyword reserved at this point) - maybe that should mean that you are allowed to set parameters via APL since the module can, if it does not want to allow that, give all parameters explicitly. 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-6990) Unable to specify RPM with architecture in tag
Title: Message Title
Jesse Hanley commented on PUP-6990
Re: Unable to specify RPM with architecture in tag
Here's the RPM's name: {{lustre-client-2.8.0-3.10.0_327.36.3.el7.x86_64_g58ba61a.x86_64.rpm }}
Here's an example of what happens:
{{# puppet apply -e 'package { "lustre-client": ensure => "2.8.0-3.10.0_327.36.3.el7.x86_64_g58ba61a" }
' --environment=production Notice: Compiled catalog for in environment production in 0.06 seconds Error: Could not update: Execution of '/bin/yum -d 0 -e 0 -y install lustre-client-2.8.0-3.10.0_327.36.3.el7_g58ba61a.x86_64' returned 1: Error: Nothing to do Error: /Stage[main]/Main/Package[lustre-client]/ensure: change from purged to 2.8.0-3.10.0_327.36.3.el7.x86_64_g58ba61a failed: Could not update: Execution of '/bin/yum -d 0 -e 0 -y install lustre-client-2.8.0-3.10.0_327.36.3.el7_g58ba61a.x86_64' returned 1: Error: Nothing to do Notice: Applied catalog in 0.77 seconds}}
Even specifying the architecture:
{{# puppet apply -e 'package { "lustre-client": ensure => "2.8.0-3.10.0_327.36.3.el7.x86_64_g58ba61a.x86_64" }
' --environment=production Notice: Compiled catalog for in environment production in 0.06 seconds Error: Could not update: Execution of '/bin/yum -d 0 -e 0 -y install lustre-client-2.8.0-3.10.0_327.36.3.el7_g58ba61a.x86_64.x86_64' returned 1: Error: Nothing to do Error: /Stage[main]/Main/Package[lustre-client]/ensure: change from purged to 2.8.0-3.10.0_327.36.3.el7.x86_64_g58ba61a.x86_64 failed: Could not update: Execution of '/bin/yum -d 0 -e 0 -y install lustre-client-2.8.0-3.10.0_327.36.3.el7_g58ba61a.x86_64.x86_64' returned 1: Error: Nothing to do Notice: Applied catalog in 0.79 seconds}}
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
Jira (PDOC-152) Strings should support the documentation of private classes
Title: Message Title Trevor Vaughan commented on PDOC-152 Re: Strings should support the documentation of private classes Henrik Lindberg You bring up a good point. Count this as my official vote toward adding a protected set of classes. I use assert_private() to ensure that users can't include classes that won't work without other parts of the module. This way I can strictly control, from the top level, how users should be using the module and it lets me logically split up my module into components. However, I do *not* want to have to repeat all 5 million parameters at the top level, that defeats a lot of the reason that I'm splitting things off into sub-classes. What I want is what I currently have, which I guess you could call protected, where I can control the class acesss and inclusion order and I can then allow the setting of various less-used parameters via data binding. Alternatively, classes could be private with parameters having a flag to be public or something like that. That said, my current parameters are already going over 140 characters and I'm starting to think that .h files are about to come back into style. 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-6995) Running "puppet master --compile" as root will cause future compiles for that node to fail
Title: Message Title Henrik Lindberg commented on PUP-6995 Re: Running "puppet master --compile" as root will cause future compiles for that node to fail Makes sense to set the userid when compiling, or you would not be sure if the compile will work or not when contacting the master. It also makes sense to not have a writeable cache when using master --compile, it should not write anything anyway since it is looking up a node. Writing node information obtained from the command line (if that is what it is actually doing) seems bad. We may have something similar to look at in Catalog Preview since it is basically the same as master --compile. 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-6984) alias on Package/Exec resources produces misleading warning
Title: Message Title Henrik Lindberg commented on PUP-6984 Re: alias on Package/Exec resources produces misleading warning Hear you... I said "I think I would" - which is to say that I don't really know. Your input on this matters. 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 (PDOC-152) Strings should support the documentation of private classes
Title: Message Title Henrik Lindberg commented on PDOC-152 Re: Strings should support the documentation of private classes Not sure I follow the reasoning here - if you can set the parameters from outside, then the construct is not really private is it? There is still value in producing documentation of private elements of the language for the purpose of helping those that maintain a module. Note that there will be proper support for private classes built into the puppet language. When that has been added, the @private yard tag can be inferred for those classes. Don't think it is worth digging out the use of assert_private as that will be replaced by the support in the language itself. 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-6781) support 'verbatim' lookup option
Title: Message Title Henrik Lindberg commented on PUP-6781 Re: support 'verbatim' lookup option merged to master at: f026e9e 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-6624) File resource with source=http:// not updating on url change
Title: Message Title Stefan commented on PUP-6624 Re: File resource with source=http:// not updating on url change Can I get an update on that issue? Is it confirmed? Do you have an idea on how to fix it? Is it on the roadmap? Do you need anything from 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-6981) Reroute hiera_xxx functions to the new lookup logic
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6981 Reroute hiera_xxx functions to the new lookup logic 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.
