Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4428) The 'err' logging function cannot be called as a statement
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4428 The 'err' logging function cannot be called as a statement Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4438) Add required_repeated_param to 4.x function API
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4438 Add required_repeated_param to 4.x function API Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4436) With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-4436
With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail
Change By:
Eric Sorenson
Release Notes:
BugFix
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4193) Add ability to use a lambda as case option for advanced matching
Title: Message Title Eric Sorenson commented on PUP-4193 Re: Add ability to use a lambda as case option for advanced matching Yes, I'd like to see this change go through the newly-streamlined Puppet RFC process rather than go straight in to the language. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title Eric Sorenson commented on PUP-4193 Re: Add pattern matching to the Puppet DSL This seems pretty neat, and it's not super hard to understand but I'd love to see a real example of a module author making use of it. Two questions for Nicholas Fagerlund: is the language spec and sample code here enough to doc this change, and is that work covered with [DOC-1925]? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-835) Add facter support for RHEL 7 base facts
Title: Message Title Eric Sorenson commented on FACT-835 Re: Add facter support for RHEL 7 base facts I'm unable to reproduce this on Facter 2.4.3: [vagrant@glitched ~]$ more /etc/redhat-release CentOS Linux release 7.0.1406 (Core) [vagrant@glitched ~]$ facter netmask 255.255.255.0 [vagrant@glitched ~]$ facter macaddress 00:0c:29:08:9e:99 [vagrant@glitched ~]$ facter interfaces ens32,lo Can you provide more information about the underlying hardware?
Jira (PUP-3068) 'basemodulepath' doesn't expand relative path elements correctly
Title: Message Title Eric Sorenson commented on PUP-3068 Re: 'basemodulepath' doesn't expand relative path elements correctly Comment from Joshua Partlow on a possible implementation path: You can have relative paths in our environment.conf $modulepath, and they will be made absolute relative to the envdir. This could probably work for basemodulepath if we figure out where in the settings bootstrapping it's getting made absolute and perhaps provide the raw basemodulepath to the EnvironmentConf object. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-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 Name: Rehabilitate Iterateon directory environments environmentconfig Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4555) Iterate on directory environments
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4555 Iterate on directory environments Change By: Eric Sorenson Summary: Rehabilitate Iterateon directoryenvironments Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4472) Obscure sensitive passwords in Puppet runs
Title: Message Title Eric Sorenson assigned an issue to Eric Sorenson I'm going to mark this as a duplicate of an earlier ticket that describes the same requirement. Please follow PUP-1974 to track the implementation progress. Puppet / PUP-4472 Obscure sensitive passwords in Puppet runs Change By: Eric Sorenson Resolution: Duplicate Assignee: EricSorenson Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this
Jira (PUP-3068) 'basemodulepath' doesn't expand relative path elements correctly
Title: Message Title Eric Sorenson commented on PUP-3068 Re: 'basemodulepath' doesn't expand relative path elements correctly Got a concrete use-case from a customer that I thought would be worth recording here. At the heart of it, the problem is that each environment's directory contains two distinct sets of modules, the default $confdir/environments/$environment/modules, which contains Forge modules, and a second one, $confdir/environments/$environment/site_modules, which contains locally-authored modules. While it would be possible to put an environment.conf in every environment, this is a ton of work and repetitive code. There are hundreds of environments, so duplicating the one-line environment.conf to all of them seems wrong-headed; it would be way better if the same config could simply be placed once, globally. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4555) Rehabilitate directory environments
Title: Message Title Eric Sorenson created an issue Puppet / PUP-4555 Rehabilitate directory environments Issue Type: Epic Assignee: Nicholas Fagerlund Components: DOCS, Server Created: 2015/05/11 2:02 PM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Eric Sorenson Through the development of directory environments in 2014, new requirements and use-cases emerged and new settings/features were added to accommodate them. We ended up with a pretty complicated system that still missed a couple of common workflows. This epic is to gather lessons learned and design requirements for the next iteration of directory environments, with the goal of simplifying the UX and cognitive load while meeting the requirements. Add Comment
Jira (PUP-4555) Rehabilitate directory environments
Title: Message Title Eric Sorenson assigned an issue to Eric Sorenson Puppet / PUP-4555 Rehabilitate directory environments Change By: Eric Sorenson Assignee: NicholasFagerlund EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4555) Rehabilitate directory environments
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4555 Rehabilitate directory environments Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1974) Mechanism for securing sensitive catalog data
Title: Message Title Eric Sorenson commented on PUP-1974 Re: Mechanism for securing sensitive catalog data There's a pretty simple precedent in the chef world that's simply a common attribute (err, 'metaparameter' in puppet-land) called 'sensitive', which prevents content logging: https://docs.chef.io/resource_common.html#attributes Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-835) Add facter support for RHEL 7 base facts
Title: Message Title Eric Sorenson assigned an issue to Brook Shelley Facter / FACT-835 Add facter support for RHEL 7 base facts Change By: Eric Sorenson Assignee: EricSorenson BrookShelley Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4555) Iterate on Directory Environments
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4555 Iterate on Directory Environments Change By: Eric Sorenson Summary: IterateonDirectoryEnvironments ! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-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 Name: Iterateon directoryenvironmentconfig DirectoryEnvironments! Summary: Iterateon directoryenvironments DirectoryEnvironments! Throughthedevelopmentofdirectoryenvironmentsin2014,newrequirementsanduse PUP - casesemergedandnewsettings/featureswereaddedtoaccommodatethem.Weendedupwithaprettycomplicatedsystemthatstillmissedacoupleofcommonworkflows.Thisepicistogatherlessonslearnedanddesignrequirementsfor 4555has the nextiterationofdirectoryenvironments,withthegoalofsimplifyingtheUXandcognitiveloadwhilemeetingtherequirements details . Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson commented on PUP-4380 Re: Split non-core puppet functionality into modules I flipped that spreadsheet's permissions to public. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-628) facter returns incorrect value for `facter virtual` for Ldoms due to how the fact is added in Solaris.
Title: Message Title Eric Sorenson updated an issue Facter / FACT-628 facter returns incorrect value for `facter virtual` for Ldoms due to how the fact is added in Solaris. Change By: Eric Sorenson Affects Version/s: FACT2.3.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-628) facter returns incorrect value for `facter virtual` for Ldoms due to how the fact is added in Solaris.
Title: Message Title Eric Sorenson commented on FACT-628 Re: facter returns incorrect value for `facter virtual` for Ldoms due to how the fact is added in Solaris. Kylo Ginsberg this came up again as a customer escalation, could you pull it in for an upcoming sprint to have someone investigate? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson commented on PUP-4380 Re: Split non-core puppet functionality into modules Justin Stoller yes, I envision there being two possible destinies for the modules thus extracted: supported module - goes to puppetlabs namespace - probably not to the module eng team as they mostly work on application modules like puppetlabs-mysql and these are kind of categorically different, so it seems unreasonable to put that burden on them. approved module - goes to puppetlabs-community namespace - these would be more OS-specific types and providers that make sense to open up commit access, such as the Mac OS X and *BSD providers. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4468) AIO Upgrade Module
Title: Message Title Eric Sorenson commented on PUP-4468 Re: AIO Upgrade Module Yes it should definitely be supported. It should not be PE-only, as it affects everyone taking a 3.x infrastructure to Puppet 4. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Eric Sorenson Affects Version/s: PUP3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Eric Sorenson commented on PUP-4520 Re: Future parser is not correctly handling the default case of a case statement OK I was able to reproduce but it's weirdly something that seems to affect the PE 3.8.0 version and not OSS Puppet 3.7.5 (or, incidentally, Puppet 4) PE: [vagrant@deglitch ~]$ puppet apply --parser future /Sandbox/pup-4520.pp Notice: Compiled catalog for deglitch.local in environment production in 0.36 seconds Notice: default case Notice: /Stage[main]/Main/Notify[default case]/message: defined 'message' as 'default case' Notice: Finished catalog run in 0.02 seconds [vagrant@deglitch ~]$ puppet --version 3.7.5 (Puppet Enterprise 3.8.0-rc0-532-ga37f033) And on FOSS: [vagrant@glitcher ~]$ puppet apply --parser future /Sandbox/pup-4520.pp
Jira (PUP-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Eric Sorenson Component/s: Language Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Eric Sorenson commented on PUP-4520 Re: Future parser is not correctly handling the default case of a case statement I think this is actually due to your stringify_facts setting on the agent/apply side. I get the correct answer with --no-stringify_facts and the default case without, regardless of the order of the statements. [vagrant@glitcher ~]$ puppet apply --parser future ./enterprise-665.pp Notice: Compiled catalog for glitcher.local in environment production in 0.42 seconds Notice: default case Notice: /Stage[main]/Main/Notify[default case]/message: defined 'message' as 'default case' Notice: Finished catalog run in 0.01 seconds [vagrant@glitcher ~]$ puppet apply --parser future --no-stringify_facts ./enterprise-665.pp Notice: Compiled catalog for glitcher.local in environment production in 0.43 seconds Notice: nondefault case Notice: /Stage[main]/Main/Notify[nondefault case]/message: defined 'message' as 'nondefault case'
Jira (PUP-4464) 4.x parser bug with anonymous data structures
Title: Message Title
Eric Sorenson created an issue
Puppet / PUP-4464
4.x parser bug with anonymous data structures
Issue Type:
Bug
Affects Versions:
PUP 4.0.0
Assignee:
Unassigned
Components:
Language
Created:
2015/04/27 12:38 PM
Priority:
Normal
Reporter:
Eric Sorenson
A user reported via IRC, and Richard Clamp repro'ed, the following issue using anonymous data structures to iterate over. The short version is that using an array, then a hash, confuses the parser, but hash then array works. So this is OK:
class munin {
Jira (PUP-927) puppet apply on Windows always uses *nix style newlines from templates
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-927 puppet apply on Windows always uses *nix style newlines from templates Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4113) Migrate and Preview 3.8 Language to 4.0
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4113 Migrate and Preview 3.8 Language to 4.0 Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4437) Update the puppet-agent Repo for 4.0.1 to Incorporate Fix for PUP-4390
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4437 Update the puppet-agent Repo for 4.0.1 to Incorporate Fix for PUP-4390 Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4345) Port PUP-3388 Issue Creating Multiple Mirrors in Zpool Resource to PUP 3.8
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4345 Port PUP-3388 Issue Creating Multiple Mirrors in Zpool Resource to PUP 3.8 Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4190) CLONE - Puppet device displays credentials in plain text when run manually
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4190 CLONE - Puppet device displays credentials in plain text when run manually Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4201) Add support for structured logging
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4201 Add support for structured logging Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4186) Backport Weekly tasks always notify 'trigger changed' to Puppet 3.8
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4186 Backport Weekly tasks always notify 'trigger changed' to Puppet 3.8 Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4187) Backport Puppet should execute ruby.exe not cmd.exe when running as a Windows to Puppet 3.8
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4187 Backport Puppet should execute ruby.exe not cmd.exe when running as a Windows to Puppet 3.8 Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Eric Sorenson commented on PUP-2630 Re: Server-set global variables like $::environment get overwritten by client facts Ultimately removing them from top-scope seems correct. It is certain that having $environment set as a top-scope variable is confusing, because many people think that setting it either via ENC, a fact, or simply at top scope in a manifest, will change the actual Puppet Environment. However, having the server_facts() function as the only solution seems inconsistent to me, because here we have a set of data akin to trusted facts and facter facts, and indeed reference/documented alongside of them, but which is NOT populated into a top scope (immutable, as with $trusted['foo']) hash. Would be interested in others' opinions about that, but I'd prefer them to all be the same even if it means setting yet another global variable name. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4185) Backport ability to add a member to group to Puppet 3.8
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4185 Backport ability to add a member to group to Puppet 3.8 Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4460) 'statefile' is never pruned of files no longer in management
Title: Message Title Eric Sorenson created an issue Puppet / PUP-4460 'statefile' is never pruned of files no longer in management Issue Type: Bug Assignee: Unassigned Created: 2015/04/23 4:38 PM Priority: Normal Reporter: Eric Sorenson The 'statefile' (state.yaml) never cleans up entries which USED to be under management but are no longer in the catalog. This causes the statefile to grow without cleanup, and there could be a bunch of extra work puppet does on intialization that could be totally unneeded. I made a short gist that exercises the problem: https://gist.github.com/ahpook/52d80c597da59aebfada An interesting question that arose through this exploration: What is the purpose of the statefile? The setting help text is kind of untrue: # Where puppet agent and puppet master store state associated # with the running configuration. In the case of puppet master, # this
Jira (PUP-42) Support data and puppet extensions contributed from modules
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-42 Support data and puppet extensions contributed from modules Change By: Eric Sorenson Epic Name: Supportdataandpuppetextensionscontributedfrommodules DatainModules Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4390) Regression: Windows service provider fails to retrieve current state on 2003
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4390 Regression: Windows service provider fails to retrieve current state on 2003 Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4336) puppet apply --trace has stopped producing output
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4336 puppet apply --trace has stopped producing output Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3653 Unable to create/force empty Windows groups Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3863) hiera('some::key', undef) returns empty string
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3863
hiera('some::key', undef) returns empty string
Change By:
Eric Sorenson
Release Notes:
BugFix
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1628) Add mount provider for AIX
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1628 Add mount provider for AIX Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4090 Zypper provider doesn't work correctly on SLES 10.4 with install_options set Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4379) Future parser interpolation with [] after variable prefixed with underscore
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4379 Future parser interpolation with [] after variable prefixed with underscore Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4341) add acceptance test for puppet apply --trace
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4341 add acceptance test for puppet apply --trace Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4277) Case and Selector match should be deep
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4277 Case and Selector match should be deep Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4278) unless with else when then part is empty produces nil result (future parser)
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4278 unless with else when then part is empty produces nil result (future parser) Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1291 scheduled_task : add support for every X minutes or hours mode Change By: Eric Sorenson Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3804) User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3804 User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message Change By: Eric Sorenson Release Notes: BugFix NewFeature Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3804) User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3804 User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4334) hiera_include stopped working
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4334 hiera_include stopped working Change By: Eric Sorenson Release Notes: BugFix Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4328) scope.lookupvar does not work in ERB templates (future parser)
Title: Message Title Eric Sorenson commented on PUP-4328 Re: scope.lookupvar does not work in ERB templates (future parser) Can someone please paste an example error message that users will see now? (If that error is misleading or obtuse, is it relatively easy to add a more specific message so this isn't just a RTFM problem?) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1036) Create design/estimates around Console reporting needs
Title: Message Title Eric Sorenson assigned an issue to Eric Sorenson PuppetDB / PDB-1036 Create design/estimates around Console reporting needs Change By: Eric Sorenson Assignee: KennethBarber EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3425) resource_type face search/find returns empty results
Title: Message Title Eric Sorenson commented on PUP-3425 Re: resource_type face search/find returns empty results Henrik Lindberg if there is an underlying API change (such as requiring a call to set the environment) we should definitely document that. the only changes to Faces per se that I'm aware of roadmapping were the simplifications to remove the versioned commands since those were kind of broken (and turned out not to be helpful) anyway. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4363) Support splay in apply as well
Title: Message Title Eric Sorenson commented on PUP-4363 Re: Support splay in apply as well This seems OK to me, I guess, as long as it defaults to false and needs to be enabled. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson created an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Issue Type: Bug Assignee: Unassigned Created: 2015/04/06 5:13 PM Priority: Normal Reporter: Eric Sorenson To reduce the surface area of puppet itself and increase maintainability of non-core puppet, things which can be split out from it should be. Prime examples include the Nagios types (Redmine #4146 / PUP-1077) and some of the more esoteric single-OS types/providers like solaris zpools. These could still be combined at packaging time but the puppet repository itself would not contain them. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Eric Sorenson Business Value: 452 Epic Name: Movenon-coreT/Ptomodules Epic Status: ToDo Workflow: ScrumTeam EngineeringEpic Workflow Issue Type: Bug Epic Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop
Jira (PUP-4189) Add all per-user directories to file_paths specification
Title: Message Title Eric Sorenson commented on PUP-4189 Re: Add all per-user directories to file_paths specification The paths look good to me too. And I don't think we can change these after it goes final. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4361) Puppet 4 Language fixes/enhancements
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4361 Puppet 4 Language fixes/enhancements Change By: Eric Sorenson Summary: Thisisacatch-allforbug Puppet4Language fixes/enhancements thatarisefromPuppet4Parserchanges Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-598) local groups should be modified irrespective of users being in LDAP
Title: Message Title Eric Sorenson commented on PUP-598 Re: local groups should be modified irrespective of users being in LDAP Yeah I'm not sure why we wouldn't want platform-neutral provider support for core types also in core. I'm +1 on taking this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4114) Add preview subcommand
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-4114
Add preview subcommand
Change By:
Eric Sorenson
Addanewsubcommandcalled{{preview}}inthenewmodulecreatedinPUP-4149.Thissubcommandisamodifiedversionofthe{{puppetmaster\-\-compile}}subcommandthatinadditiontocompilingacataloginanode'senvironmentalsocompilesapreviewcataloginthegiventargetenvironment.Thecommandtakestherequiredoption{{\-\-target_environmentenv}}.ThediffoutputshouldbeinJson,andplacedunderadirectoryspecifiedinanewsetting{{preview_output_dir}}andnamedafterthenodeas{{diff_$\{preview_env_name\}_$\{nodename\}.json}}.ThediffshouldbeexpressedinawaysimilartotheJUnitXMLformat-e.g.asasetofexamples/assertionsthatfailed,thereasontheyfailed,andreferencestothesourceforbothexpectedandactualoutcome(whenpossible).Thecatalogfromthepreviewenvironmentcompilationshouldbeoutputas{{preview_$\{preview_env_name\}_$\{nodename\}.json}}.Theoriginalbaselinecatalogshouldbeoutputas{{baseline_$\{baseline_env_name\}_$\{nodename\}.json}}.Thespecificationofthisformatshouldbeplacedinthemodule'srepository.Itshouldcontain:*nodename*timestamp*originalenvironmentname*previewenvironmentname*thetotalnumberofassertions*thenumberofpassedassertions*thenumberoffailedassertions*assertionresultsAjasonschemashouldbewrittenandbeincludedinthemodule'srepositorytoservebothforunittestingthatoutputcomplieswiththespecifiedformat,andasformatdocumentationforthosethatwanttoprocesstheoutput.The{{diff_}},{{preview_}},and{{baseline_}}filesareoverwrittenoneachinvocationofthe{{preview} } commandinvocationforagivennode/environmentcombination.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Sorenson commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. We have some very old performance docs here: https://docs.puppetlabs.com/puppet/#tuning-and-scaling There are recent docs that only cover puppet-server here: https://docs.puppetlabs.com/pe/latest/config_puppetserver.html Neither of these are ideal though. There already is long-form documentation that describes the different timeout settings here: http://docs.puppetlabs.com/puppet/3.7/reference/environments_configuring.html#environmenttimeout but I agree it should be punched up in the inline doc for the setting and be made a Release Note headline. I do not think we should emit log messages or warnings. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Sorenson commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. cc Jorie Tappa and Nicholas Fagerlund for the docs implications. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1277) puppetdb-ssl-setup does not accomodate PATH for puppet in AIO
Title: Message Title Eric Sorenson updated an issue PuppetDB / PDB-1277 puppetdb-ssl-setup does not accomodate PATH for puppet in AIO Change By: Eric Sorenson Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Sorenson created an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Henrik Lindberg Components: DOCS, Server Created: 2015/03/06 11:36 AM Priority: Normal Reporter: Eric Sorenson We've gone back and forth on this a few times ( PUP-2702 , PUP-2639 ) but after running into issues from PS engagements to training to this puppet-dev thread, it seems the best option is actually to default the environment_timeout to 0 (do not cache) and let people tune upwards if they need to. Please set the default to 0 for Puppet 4, and let's update the docs to describe the rationale there.
Jira (PDB-1277) puppetdb-ssl-setup does not accomodate PATH for puppet in AIO
Title: Message Title Eric Sorenson commented on PDB-1277 Re: puppetdb-ssl-setup does not accomodate PATH for puppet in AIO Hi, I bumped the priority of this bug to 'major' since it would be pretty rotten to have an AIO+Puppet Server RC build that won't work with PuppetDB. I see that it's slated for the next sprint, which is fine, but can you please bump it to the head of the queue for work as early as possible in the sprint? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4014) Add PKINIT support to Puppet CA
Title: Message Title Eric Sorenson assigned an issue to Eric Sorenson Puppet / PUP-4014 Add PKINIT support to Puppet CA Change By: Eric Sorenson Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4076) Remove the 'allow_virtual' warning in the 3.x series
Title: Message Title Eric Sorenson commented on PUP-4076 Re: Remove the 'allow_virtual' warning in the 3.x series thanks Kylo, lots of support + OSS bugs against this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4066) With strict variables turned on, it is difficult to use built in variables
Title: Message Title Eric Sorenson commented on PUP-4066 Re: With strict variables turned on, it is difficult to use built in variables Would that change have helped the sort of problem that is on the puppetlabs-apt module (https://github.com/puppetlabs/puppetlabs-apt/pull/449 for example)? If so, and if Daniele Sluijters / Morgan Haskel / Hunter Haugen agree, I say go for it. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Eric Sorenson commented on PUP-3986 Re: Expand predefined OID's for Puppet's extension attributes They're canonically documented here: https://docs.puppetlabs.com/puppet/latest/reference/ssl_attributes_extensions.html#puppet-specific-registered-ids Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3948
Let lookup be the impl for agnostic lookup of data
Change By:
Eric Sorenson
Withthenewagnosticdatainmodules(andenvironments)introducedinPUP-1640wereallyneedawaytousethedataprovidedinotherwaysthanjustbindingclassparameters.Wecurrentlyhaveafunctioncalled{{lookup}}thatlooksupinPuppetBinder,andtheninhiera.Thisfunctionalityisnot particularily particularly valuabletousersastheyaremostlikelynotgoingtousetheBinderforanythingdirectlylookedupfromPuppetLanguagecode.Instead,weshouldrepurpose{{lookup}}tobethe equivalence equivalent ofthe{{hiera}}function,andadd eitheradd optionstoittodothe equivalence equivalent of{{hiera_array}} , and{{hiera_hash}}. The{{hiera_include}} function isnotreallyneeded,butcouldalsobeconsidered.({{hiera_include}}isthesameasalookupfollowedbyaniterationthatdoesinclude-e.g:{code}#litkethislookup('classes').each|$c|{include$c}#orlikethisincludelookup('classes'){code}Thelookupargumentsarealreadyquiterich,andaddingsupportformergelookupofarrayandhashcouldbeaddedasadditionaloptionsratherthanseparatefunctions,althoughthereareadditionaloptionswhenusingthehashmerge( specifically, passingoptiononto'deeper'merge)thatmaywarrantseparatingthem.Thishasconsequencesonthedataproviders:*theymustgetthesameoptions(or else alayeredbackendsuchashieracannotdothemerge,andwillnotexposeitsinternalstothecaller,socallercannotdomerge).*therecursionlockingmustbedonewithoutpassinganargumentsinceabackendmaycallcodethatinturncannotpasstherecursionlockon.AsolutionfortherecursionlockingistouseaPuppet.contextandseta{{look_up_key_lock}}hashthattheimplementationscanusetocheckthelock.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3948
Let lookup be the impl for agnostic lookup of data
Change By:
Eric Sorenson
Withthenewagnosticdatainmodules(andenvironments)introducedinPUP-1640wereallyneedawaytousethedataprovidedinotherwaysthanjustbindingclassparameters.Wecurrentlyhaveafunctioncalled{{lookup}}thatlooksupinPuppetBinder,andtheninhiera.ThisfunctionalityisnotparticularlyvaluabletousersastheyaremostlikelynotgoingtousetheBinderforanythingdirectlylookedupfromPuppetLanguagecode.Instead,weshouldrepurpose{{lookup}}tobetheequivalentofthe{{hiera}}function,andaddoptionstoittodotheequivalentof{{hiera_array}}and{{hiera_hash}}.The{{hiera_include}}functionisnotreallyneeded,butcouldalsobeconsidered.({{hiera_include}}isthesameasalookupfollowedbyaniterationthatdoesinclude-e.g:{code}# litke like thislookup('classes').each|$c|{include$c}#orlikethisincludelookup('classes'){code}Thelookupargumentsarealreadyquiterich,andaddingsupportformergelookupofarrayandhashcouldbeaddedasadditionaloptionsratherthanseparatefunctions,althoughthereareadditionaloptionswhenusingthehashmerge(specifically,passingoptiononto'deeper'merge)thatmaywarrantseparatingthem.Thishasconsequencesonthedataproviders:*theymustgetthesameoptions(orelsealayeredbackendsuchashieracannotdothemerge,andwillnotexposeitsinternalstothecaller,socallercannotdomerge).*therecursionlockingmustbedonewithoutpassinganargumentsinceabackendmaycallcodethatinturncannotpasstherecursionlockon.AsolutionfortherecursionlockingistouseaPuppet.contextandseta{{look_up_key_lock}}hashthattheimplementationscanusetocheckthelock.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (FACT-825) Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems
Title: Message Title Eric Sorenson commented on FACT-825 Re: Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems Kylo Ginsberg could someone on your team take a look at this? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-825) Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems
Title: Message Title Eric Sorenson assigned an issue to Kylo Ginsberg Facter / FACT-825 Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems Change By: Eric Sorenson Assignee: EricSorenson KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4014) Add PKINIT support to Puppet CA
Title: Message Title Eric Sorenson commented on PUP-4014 Re: Add PKINIT support to Puppet CA Hi Michael Weiser – thanks for this work! It's very interesting but tbh I do not understand much of the operating conditions/constraints that led you to add this feature, so it's tough to say yes we should merge this. (For context, I'm the product manager for Puppet so I try to talk to as many users as possible and balance their problems against engineering constraints to determine the best course of action for the project.) Can you help me understand the environment you're working in and the limitations of the current codebase (especially why you can't use autosign policy+custom CSR attributes) that led you to need this change? From Puppet's perspective, it's a little scary to accept this patch because it changes some deep and not-well-understood parts of the codebase in ways that are not in line with a common use-case, so we really want to make sure we're not going to change behaviour in unexpected ways before merging it. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3809
Separate code (content?) and configuration directories for AIO packaging
Change By:
Eric Sorenson
Therehasbeenathreadgoingaroundbetweensomeengineeringfolksandsomereleasefolksabouttheneedforseparatingcode(orcontent)andconfigurationintotwodistinctdirectories.ThiswillmakeiteasiertosynctheappropriatefilesaroundtomultiplemastersviatheforthcomingFileSyncservice.Thefilesystemlayoutshouldlooklike:{code}#locationsfor'puppet*'subcommandconfigfiles(agent,apply,master)/etc/puppetlabs/puppet/{puppet,auth,fileserver}.conf=canonicalconfigdirectory/etc/puppetlabs/puppet/ssl=puppet'ssslcerts#separatepuppetprojectsgettheirownconfigdirectoriesatthislevel/etc/puppetlabs/puppetserver=puppetserverconfigdir/etc/puppetlabs/puppetdb=puppetdbconfigdir#'code'constructs(i.e.inputsintoacatalog)gotonew'code'directory#thisisusuallythecheckoutofar10kcontrolrepo/etc/puppetlabs/code=codedirincludeshiera.yaml,hieradata,modules,manifests/etc/puppetlabs/code/environments/=defaultlocationfor'$environmentpath'#binaries and , libraries ,modulesshippedwiththepackage liveunder/opt/puppetlabs/opt/puppetlabs/bin=symlinktargetfor'puppet','puppetserver','puppetdb',etc./opt/puppetlabs/puppet=newruby-puppetroot(bin,lib,cache,plugins,include,shareunderneath)/opt/puppetlabs/ puppet/modules=systemmodulepath/opt/puppetlabs/ server=serversideappsliveunderneath/opt/puppetlabs/server/puppetserver/ #stateandlogdirectories/var/run/puppetlabs=pidfilesgohere/var/log/puppetlabs=logfilesgohere{code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Jeff: /etc/puppetlabs/puppet has all the config, and these files are usually managed by puppet modules and therefore are not checked in directly. /etc/puppetlabs/code has code, and is the root of an r10k control repository. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Chris the config files are not in the same directory as bin lib et al. They are in /etc/puppetlabs/puppet and the bin are in *OPT*/puppetlabs/puppet. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3809 Separate code (content?) and configuration directories for AIO packaging Change By: Eric Sorenson Therehasbeenathreadgoingaroundbetweensomeengineeringfolksandsomereleasefolksabouttheneedforseparatingcode(orcontent)andconfigurationintotwodistinctdirectories.ThiswillmakeiteasiertosynctheappropriatefilesaroundtomultiplemastersviatheforthcomingFileSyncservice. Ineedtoaddmoredetailtothisticket,butitneedstolandinPuppet4inordertocoincidewiththeAIOpackagingefforts.FornowIjustwantedtogetsomethingcapturedandflaggedasPuppet4.0.0sothattheworkdoesnotslipthroughthecracks. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3809
Separate code (content?) and configuration directories for AIO packaging
Change By:
Eric Sorenson
Therehasbeenathreadgoingaroundbetweensomeengineeringfolksandsomereleasefolksabouttheneedforseparatingcode(orcontent)andconfigurationintotwodistinctdirectories.ThiswillmakeiteasiertosynctheappropriatefilesaroundtomultiplemastersviatheforthcomingFileSyncservice.Thefilesystemlayoutshouldlooklike:{code} #locationsfor'puppet*'subcommandconfigfiles(agent,apply,master)/etc/puppetlabs/puppet/{puppet,auth,fileserver}.conf=canonicalconfigdirectory/etc/puppetlabs/puppet/ssl=puppet'ssslcerts#separatepuppetprojectsgettheirownconfigdirectoriesatthislevel/etc/puppetlabs/puppetserver=puppetserverconfigdir/etc/puppetlabs/puppetdb=puppetdbconfigdir#'code'constructs(i.e.inputsintoacatalog)gotonew'code'directory#thisisusuallythecheckoutofar10kcontrolrepo/etc/puppetlabs/code=codedirincludeshiera.yaml,hieradata,modules,manifests/etc/puppetlabs/code/environments/=defaultlocationfor'$environmentpath'#binariesandlibrariesliveunder/opt/puppetlabs/opt/puppetlabs/bin=symlinktargetfor'puppet','puppetserver','puppetdb',etc./opt/puppetlabs/puppet=newruby-puppetroot(bin,lib,cache,plugins,include,shareunderneath)/opt/puppetlabs/server=serversideappsliveunderneath/opt/puppetlabs/server/puppetserver/#stateandlogdirectories/var/run/puppetlabs=pidfilesgohere/var/log/puppetlabs=logfilesgohere{code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging I'm gonna call this consensus and update the relevant places. Folks who were blocked on this decision, are you now unblocked? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Eric Sorenson commented on HI-298 Re: Update FS layout for hiera to the changes, description matches my expectation. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3809
Separate code (content?) and configuration directories for AIO packaging
Change By:
Eric Sorenson
Therehasbeenathreadgoingaroundbetweensomeengineeringfolksandsomereleasefolksabouttheneedforseparatingcode(orcontent)andconfigurationintotwodistinctdirectories.ThiswillmakeiteasiertosynctheappropriatefilesaroundtomultiplemastersviatheforthcomingFileSyncservice. Thefilesystemlayoutshouldlooklike:{code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Yes that's correct Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging yes, but it's not wrong. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Jeff – in talking through this, it's more than master and agent service: if you want a different directory for master/puppet.conf, it'd also make sense to have an apply subdir, and it becomes ambiguous where the other puppet subcommand tools like puppet cert ought to look. New tools ought to get a split-out directory as makes sense for their configs (puppetserver for example) but as long as there is a bundle of functionality all lumped into one thing called 'puppet' its config should live together. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging A couple of comments here after poking around in an actual AIO-installed setup for a bit at Contrib Summit with Dominic Cleal Stefan Goethals Julien Pivotto Justin Stoller. The code/ directory shouldn't live under agent/, as none of its contents are used by an agent. They are either used by a master or by puppet apply; my suggestion would be to move that up a directory to live directly under /etc/puppetlabs. Similarly, the hiera.yaml config location lands in a weird/wrong place, but it's less obvious where it should go, other than perhaps /etc/puppetlabs/hiera/ since it's technically a separate project and set of configuration. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Ah, yep, under code/ is correct – In the current version it landed in /etc/puppetlabs/agent/hiera.yaml Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3922 Preserve modulepath structure during pluginsync Change By: Eric Sorenson Summary: Pluginsynccollisions Preservemodulepathstructureduringpluginsync Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3922
Preserve modulepath structure during pluginsync
Change By:
Eric Sorenson
Originalproblemreportfrom[~ben.ford]:{quote}Ihadaproblemcomeupintraininglastweekinvolvingsyncedfactsthatbroughtoutalargerprobleminpluginsync.SoifIcreateamodule'one'anddefineafactinitcalled'myfact',thencreateamodule'two'andalsodefineafacttherecalled'myfact'theywillcollide.Thefactin'two'willwinbecauseitcomeslaterinthedirectoryglobbing.Butworseisthattheywillbecontinuouslyfighting.Onanagentrunyoucanseethisfactbeingoverwrittento'one/myfact'andthen'two/myfact'everysingletime.Thisishorribleforusabilitybecauseit'snotclearwhichfactwillbecalled,andit'saterriblewasteofbandwidth,etc.{quote}Mycommentfromtwoyearsago:{quote}Thenamespacing/loadorderisproblematicbutthefilesbeingcopiedontopofoneanotherwouldbefixedifwereplicatedthemodulepathstructurefromthemasterontotheclientinsteadofsquashingeverythinginto$plugindestregardlessofsource.{quote}Itturnsoutthatthisproblemblockedourabilitytoexecuteon[PUP-1077],becausenewerversionsofamodule,installedviapluginsync,whichrestructuredfileswouldincompletelyoverlay thesamemodulestructureincludedinapackage'smodulepath.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3922 Preserve modulepath structure during pluginsync Change By: Eric Sorenson Fix Version/s: PUP4.x Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3922 Preserve modulepath structure during pluginsync Change By: Eric Sorenson Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3922) Pluginsync collisions
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3922 Pluginsync collisions Change By: Eric Sorenson Reporter: redmine.exporter EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3922
Preserve modulepath structure during pluginsync
Change By:
Eric Sorenson
Originalproblemreportfrom[~ben.ford]:{quote} Ihadaproblemcomeupintraininglastweekinvolvingsyncedfactsthatbroughtoutalargerprobleminpluginsync.SoifIcreateamodule'one'anddefineafactinitcalled'myfact',thencreateamodule'two'andalsodefineafacttherecalled'myfact'theywillcollide.Thefactin'two'willwinbecauseitcomeslaterinthedirectoryglobbing.Butworseisthattheywillbecontinuouslyfighting.Onanagentrunyoucanseethisfactbeingoverwrittento'one/myfact'andthen'two/myfact'everysingletime.Thisishorribleforusabilitybecauseit'snotclearwhichfactwillbecalled,andit'saterriblewasteofbandwidth,etc. {quote}Mycommentfromtwoyearsago:{quote}Thenamespacing/loadorderisproblematicbutthefilesbeingcopiedontopofoneanotherwouldbefixedifwereplicatedthemodulepathstructurefromthemasterontotheclientinsteadofsquashingeverythinginto$plugindestregardlessofsource.{quote}Itturnsoutthatthisproblemblockedourabilitytoexecuteon[PUP-1077],becausenewerversionsofamodule,installedviapluginsync,whichrestructuredfileswouldincompletelyoverlay
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
