Jira (PUP-2930) puppet module list --render-as yaml returns excessive information
Title: Message Title
Daniel Dreier created an issue
Puppet / PUP-2930
puppet module list --render-as yaml returns excessive information
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
11/Jul/14 10:06 PM
Environment:
Debian 7 x86_64
Priority:
Minor
Reporter:
Daniel Dreier
I'm not 100% sure whether this should be a bug or improvement request, but it appears that rendering the module list as yaml displays vastly more information than either the default or the json rendering.
Compare:
root@debian7:/# puppet module list
/etc/puppet/modules
└── puppetlabs-stdlib (v4.2.2)
root@debian7:/# puppet module list --render-as json
{"environment":"production","modules_by_path":{"/etc/puppet/modules":["Module stdlib(/etc/puppet/modules/stdlib)"]}}
root@debian7:/# puppet module list --render-as yaml
---
!ruby/sym environment: production
!ruby/sym modules_by_path:
/etc/puppet/modules:
- !ruby/object:Puppet::Module
name: stdlib
path: /etc/puppet/modules/stdlib
environment: production
metadata_file: /etc/puppet/modules/stdlib/metadata.json
metadata:
name: puppetlabs-stdlib
version: "4.2.2"
author: puppetlabs
summary: "Puppet Module Standar
Jira (PUP-1244) Yum provider using "version-release" to validate installation.
Title: Message Title Jason Antman assigned an issue to Jason Antman Puppet / PUP-1244 Yum provider using "version-release" to validate installation. Change By: Jason Antman Assignee: Jason Antman Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1244) Yum provider using "version-release" to validate installation.
Title: Message Title
Jason Antman commented on an issue
Re: Yum provider using "version-release" to validate installation.
I've rebase this on the puppet-4 branch and cut https://github.com/puppetlabs/puppet/pull/2866
Add Comment
Puppet / PUP-1244
Yum provider using "version-release" to validate installation.
When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification. {code} $snmp_version = "5.3.2.2" package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Cha...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2929) Optimize the (function) loader
Title: Message Title Henrik Lindberg commented on an issue Re: Optimize the (function) loader Marked as blocking PUP-494, but not yet sure of the overall impact of the change (replacing a 47% slower than optimal lookup of function name) since it depends on the ration of function calls in the manifests. Add Comment Puppet / PUP-2929 Optimize the (function) loader The new 4x loader sub system uses the concept of a TypedName, a construct that keeps information about a name, its segments etc. This to avoid having to split a name on :: multiple times, count the number of segments etc. It also serves as a key in hashes. The performance of using this as a hash key is 20% slower than using an unfrozen string, and 47% ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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://gr
Jira (PUP-2929) Optimize the (function) loader
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2929 Optimize the (function) loader Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 11/Jul/14 4:50 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Henrik Lindberg The new 4x loader sub system uses the concept of a TypedName, a construct that keeps information about a name, its segments etc. This to avoid having to split a name on :: multiple times, count the number of segments etc. It also serves as a key in hashes. The performance of using this as a hash key is 20% slower than using an unfrozen string, and 47% slower if a frozen string is used. Instead of using a TypedName as the key, it is better to create a frozen compound key that contains both the type (the type of thing being loaded; function, class, etc) and the name. If this key has to be obtained from the TypedName via a method call, it will almost completely erase the gain
Jira (PUP-2177) PR (2494) Insecure shipped Cipher settings in Passenger example config
Title: Message Title Nicholas Fagerlund commented on an issue Re: PR (2494) Insecure shipped Cipher settings in Passenger example config I've updated the example passenger vhost at http://docs.puppetlabs.com/guides/passenger.html with the changes from the accepted pull request. Add Comment Puppet / PUP-2177 PR (2494) Insecure shipped Cipher settings in Passenger example config https://github.com/puppetlabs/puppet/pull/2494 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Brandon High assigned an issue to Brandon High Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Change By: Brandon High Assignee: Brandon High Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Brandon High updated an issue Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Change By: Brandon High Sprint: Week 2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-603) Allow to configure acceptance using github mirror
Title: Message Title Rob Reynolds commented on an issue Re: Allow to configure acceptance using github mirror Adrien Thebo I think we can file another issue for that, but I agree that we should refactor the entire structure and extract it. For now we need to move forward on just this guy. Add Comment Facter / FACT-603 Allow to configure acceptance using github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-603) Allow to configure acceptance using github mirror
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Facter / FACT-603 Allow to configure acceptance using github mirror Change By: Rob Reynolds Assignee: Eric Sorenson Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-603) Allow to configure acceptance using github mirror
Title: Message Title Rob Reynolds updated an issue Facter / FACT-603 Allow to configure acceptance using github mirror Change By: Rob Reynolds Sprint: Week 2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-614) Create structured operating system fact
Title: Message Title
William Hopper updated an issue
Facter / FACT-614
Create structured operating system fact
Change By:
William Hopper
Currently, there are several facts related to operating system based data, including:{noformat}operatingsystemoperatingsystemmajreleaseoperatingsystemreleaseosfamily{noformat}Also, there are a handful of lsb* facts for Linux systems, including:{noformat}lsbdistcodenamelsbdistdescriptionlsbdistidlsbdistreleaselsbmajdistreleaselsbrelease{noformat}These combined are a good candidate for a structured fact.Output for this fact could appear as follows (on a Linux system):{noformat}{ "osfamily" => Debian, "operatingsystem" => Debian, "release" => { "operatingsystemrelease" => 7.4, "operatingsystemmajrelease" => 7 },"lsb" => { "lsbdistid" => Debian, "lsbdistcodename" => wheezy, "lsbdistdescription" => Debian GNU/Linux 7.4 (wheezy), "lsbdistrelease" => 7.4, "lsbmajdistrelease" => 7 }}{noformat}Backwards compatibility with existing flat facts should be maintained. The naming of this structured fact is also under consideration.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-761) PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-761 PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund h2. (docs) Fix glitches noticed while backporting recent revisions to 1.6.x * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1013 Discussion|https://github.com/puppetlabs/puppetdb/pull/1013] * [Pull Request 1013 File Diff|https://github.com/puppetlabs/puppetdb/pull/1013/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PDB-760) PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-760 PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund h2. (docs) Port recent docs revisions to 1.6.x branch * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1012 Discussion|https://github.com/puppetlabs/puppetdb/pull/1012] * [Pull Request 1012 File Diff|https://github.com/puppetlabs/puppetdb/pull/1012/files] h2. Pull Request Description --... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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/
Jira (PDB-760) PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-760 PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund h2. (docs) Port recent docs revisions to 1.6.x branch * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1012 Discussion|https://github.com/puppetlabs/puppetdb/pull/1012] * [Pull Request 1012 File Diff|https://github.com/puppetlabs/puppetdb/pull/1012/files] h2. Pull Request Description --... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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/
Jira (PDB-761) PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-761 PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund h2. (docs) Fix glitches noticed while backporting recent revisions to 1.6.x * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1013 Discussion|https://github.com/puppetlabs/puppetdb/pull/1013] * [Pull Request 1013 File Diff|https://github.com/puppetlabs/puppetdb/pull/1013/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PDB-761) PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund nfagerlund commented: One lingering question on this: did implicit ordering by name go away for v3/nodes on 2.1? I think it didn't, but if it did I can amend this. Add Comment PuppetDB / PDB-761 PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund h2. (docs) Fix glitches noticed while backporting recent revisions to 1.6.x * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1013 Discussion|https://github.com/puppetlabs/puppetdb/pull/1013] * [Pull Request 1013 File Diff|https://github.com/puppetlabs/puppetdb/pull/1013/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to pu
Jira (PDB-760) PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-760 PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund Issue Type: Task Assignee: Unassigned Created: 11/Jul/14 1:12 PM Labels: github Priority: Normal Reporter: gepetto-bot (docs) Port recent docs revisions to 1.6.x branch Author: Nick Fagerlund <> Company: Github ID: nfagerlund Pull Request 1012 Discussion Pull Request 1012 File Diff Pull Request Description This commit brings over the relevant changes from commit eb20757, since PuppetDB 1.6 will stay around a while for PE customers. I applied them by hand rather than cherry-picking, to ensure no 2.1-isms would sneak over. (webhooks-id: c9319a8c6c83d34f7dafe3b33da
Jira (PDB-761) PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-761 PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund Issue Type: Task Assignee: Unassigned Created: 11/Jul/14 1:13 PM Labels: github Priority: Normal Reporter: gepetto-bot (docs) Fix glitches noticed while backporting recent revisions to 1.6.x Author: Nick Fagerlund <> Company: Github ID: nfagerlund Pull Request 1013 Discussion Pull Request 1013 File Diff Pull Request Description In 2.1 and up, the events endpoint is unsorted for v3 and v4.
Jira (FACT-612) Create structured uptime fact
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-612 Create structured uptime fact Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-612) Create structured uptime fact
Title: Message Title
William Hopper commented on an issue
Re: Create structured uptime fact
I've added a fix for the above failure at https://github.com/puppetlabs/facter/pull/726.
Add Comment
Facter / FACT-612
Create structured uptime fact
Currently, there are four flat facts for uptime: uptime_seconds, uptime_hours, uptime_days and uptime. Merging these facts into a simple structured fact would be a good kick-off for structured fact work. The output for this fact could appear as follows: {noformat} {"seconds"=>609351, "hours"=>169, "days"=>7, "uptime"=>"7 days"} {noformat} To main...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-759) PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund Pull request (docs) Revise API docs for updated info, clarity, consistency, and formatting has been closed. Add Comment PuppetDB / PDB-759 PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund h2. (docs) Revise API docs for updated info, clarity, consistency, and formatting * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1011 Discussion|https://github.com/puppetlabs/puppetdb/pull/1011] * [Pull Request 1011 File Diff|https://github.com/puppetlabs/puppetdb/pull/1011/files] h2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-bu
Jira (PDB-759) PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-759 PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund h2. (docs) Revise API docs for updated info, clarity, consistency, and formatting * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1011 Discussion|https://github.com/puppetlabs/puppetdb/pull/1011] * [Pull Request 1011 File Diff|https://github.com/puppetlabs/puppetdb/pull/1011/files] h2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-bu
Jira (PUP-2859) specify call by name / call by position
Title: Message Title Andy Parker commented on an issue Re: specify call by name / call by position I left some comments in the PR. My biggest concern is that we are using the term "call-by-name" different from the rest of the programming language community. We need to use the correct term for this, which is pass by name. Add Comment Puppet / PUP-2859 specify call by name / call by position We now have two distinct ways of calling; functions and lambdas use "call by position", and instantiation of classes and defines use "call by name". The EPP functions pass arguments to templates via "call by name". The Puppet Language Specification should document this in one place (rather than repeat the rules). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 mor
Jira (PDB-759) PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-759 PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund h2. (docs) Revise API docs for updated info, clarity, consistency, and formatting * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1011 Discussion|https://github.com/puppetlabs/puppetdb/pull/1011] * [Pull Request 1011 File Diff|https://github.com/puppetlabs/puppetdb/pull/1011/files] h2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-bu
Jira (PUP-2859) specify call by name / call by position
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2859 specify call by name / call by position Change By: Andy Parker Assignee: Andy Parker Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2859) specify call by name / call by position
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2859 specify call by name / call by position Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-612) Create structured uptime fact
Title: Message Title Kurt Wall updated an issue Facter / FACT-612 Create structured uptime fact Change By: Kurt Wall Assignee: Charlie Sharpsteen William Hopper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-612) Create structured uptime fact
Title: Message Title
Kurt Wall commented on an issue
Re: Create structured uptime fact
This failed review in master at SHA=b79c0eb5d80bd52d8b2e760e769c6b37020f8103:
$ bundle exec facter system_uptime
Could not retrieve fact='system_uptime', resolution='': uninitialized constant Facter::Util::POSIX
$ bundle exec facter -p system_uptime
{"seconds"=>256114, "hours"=>71, "days"=>2, "uptime"=>"2 days"}
Add Comment
Facter / FACT-612
Create structured uptime fact
Currently, there are four flat facts for uptime: uptime_seconds, uptime_hours, uptime_days and uptime. Merging these facts into a simple structured fact would be a good kick-off for structured fact work. The output for this fact could appear as follows: {noformat} {"seconds"=>609351, "hours"=>169, "days"=>7, "uptime"=>"7 days"} {noformat} To main...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscr
Jira (PDB-758) PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund Pull request (docs) Revise API docs for updated info, clarity, consistency, and formatting has been closed. Add Comment PuppetDB / PDB-758 PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund h2. (docs) Revise API docs for updated info, clarity, consistency, and formatting * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1010 Discussion|https://github.com/puppetlabs/puppetdb/pull/1010] * [Pull Request 1010 File Diff|https://github.com/puppetlabs/puppetdb/pull/1010/files] h2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-bu
Jira (PDB-759) PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-759 PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund Issue Type: Task Assignee: Unassigned Created: 11/Jul/14 11:24 AM Labels: github Priority: Normal Reporter: gepetto-bot (docs) Revise API docs for updated info, clarity, consistency, and formatting Author: Nick Fagerlund <> Company: Github ID: nfagerlund Pull Request 1011 Discussion Pull Request 1011 File Diff Pull Request Description This revision touches most of the pages in the v3 and v4 API docs, as well as the release notes. We've: Standardized some squirmy terminology
Jira (PDB-758) PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-758 PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund h2. (docs) Revise API docs for updated info, clarity, consistency, and formatting * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1010 Discussion|https://github.com/puppetlabs/puppetdb/pull/1010] * [Pull Request 1010 File Diff|https://github.com/puppetlabs/puppetdb/pull/1010/files] h2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-bu
Jira (PDB-758) PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund nfagerlund commented: Wrong target. Add Comment PuppetDB / PDB-758 PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund h2. (docs) Revise API docs for updated info, clarity, consistency, and formatting * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1010 Discussion|https://github.com/puppetlabs/puppetdb/pull/1010] * [Pull Request 1010 File Diff|https://github.com/puppetlabs/puppetdb/pull/1010/files] h2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PDB-758) PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-758 PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund h2. (docs) Revise API docs for updated info, clarity, consistency, and formatting * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1010 Discussion|https://github.com/puppetlabs/puppetdb/pull/1010] * [Pull Request 1010 File Diff|https://github.com/puppetlabs/puppetdb/pull/1010/files] h2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-bu
Jira (PDB-758) PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-758 PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund Issue Type: Task Assignee: Unassigned Created: 11/Jul/14 11:20 AM Labels: github Priority: Normal Reporter: gepetto-bot (docs) Revise API docs for updated info, clarity, consistency, and formatting Author: Nick Fagerlund <> Company: Github ID: nfagerlund Pull Request 1010 Discussion Pull Request 1010 File Diff Pull Request Description This revision touches most of the pages in the v3 and v4 API docs, as well as the release notes. We've: Standardized some squirmy terminology
Jira (FACT-612) Create structured uptime fact
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Facter / FACT-612 Create structured uptime fact Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-756) PR (1009): Jul 2014 docs adjustments - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1009): Jul 2014 docs adjustments - nfagerlund nfagerlund commented: Okay, thank you! I've added two commits to address your comments, so you can see what I've fixed. I'm about to close this pull request, and I'll re-open a new one targeted at stable. Add Comment PuppetDB / PDB-756 PR (1009): Jul 2014 docs adjustments - nfagerlund h2. Jul 2014 docs adjustments * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1009 Discussion|https://github.com/puppetlabs/puppetdb/pull/1009] * [Pull Request 1009 File Diff|https://github.com/puppetlabs/puppetdb/pull/1009/files] h2. Pull Request Description Lots of fun stuff! T... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-b
Jira (PDB-756) PR (1009): Jul 2014 docs adjustments - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1009): Jul 2014 docs adjustments - nfagerlund Pull request Jul 2014 docs adjustments has been closed. Add Comment PuppetDB / PDB-756 PR (1009): Jul 2014 docs adjustments - nfagerlund h2. Jul 2014 docs adjustments * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1009 Discussion|https://github.com/puppetlabs/puppetdb/pull/1009] * [Pull Request 1009 File Diff|https://github.com/puppetlabs/puppetdb/pull/1009/files] h2. Pull Request Description Lots of fun stuff! T... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-225) internationalization / localization
Title: Message Title J.D. Welch updated an issue Puppet / PUP-225 internationalization / localization Change By: J.D. Welch Assignee: J.D. Welch Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2928) Puppet tries to update the group for user when he is listed as its member twice.
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2928
Puppet tries to update the group for user when he is listed as its member twice.
Issue Type:
Bug
Assignee:
Unassigned
Created:
11/Jul/14 10:18 AM
Labels:
redmine customer
Priority:
Normal
Reporter:
redmine.exporter
When a user is found in several nss group backends ralsh shows it as being included into a group more than once and puppet continually tries to remove the user from that group.
To clarify:
I have a following resource in my manifest: user { 'tomcat7': groups => 'ssl-user', }
Until recently everything was just fine but lately the following actions began to appear: notice: /Stage[main]/Tomcat/User[tomcat7]/groups: groups changed 'ssl-user,ssl-user' to 'ssl-user'
The reason for that behaviour turned out to be the following line in /etc/nsswitch.conf: root@susegrp1:~# cat /etc/nsswitch.conf | grep group group: files ldap compat When I remove the line everything returns back to normal way.
Here is the output of actual state of resource on the system and as seen by puppet: root@susegrp1:~# id tomcat7 uid=108(tomcat7) gid=114(tomcat7) groups=301(ssl-user),114(tomcat7)
root@susegrp1:~# getent group | grep ssl-user ssl-user:x:301:tomcat7 ssl-user:x:301:tomcat7
root@susegrp1:~# ralsh user tomcat7 warning: User tomcat7 found in both useradd and useradd; skipping the useradd version user { 'tomcat7': ensure => 'present'
Jira (PUP-2626) Accept module paths in Puppet::Parser::Functions.file()
Title: Message Title
Andy Parker commented on an issue
Re: Accept module paths in Puppet::Parser::Functions.file()
Merged into master in 1bf3b4
Add Comment
Puppet / PUP-2626
Accept module paths in Puppet::Parser::Functions.file()
Allow template-style module path to be used instead of the absolute path in for the file() function. {noformat} file('example/file.ext') {noformat} would return the same as {noformat} file('/etc/puppet/modules/example/files/file.ext') {noformat}This is supposed to be like how template does module paths, where: {noformat} template('exam...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Issue Type: New Feature Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Client Created: 11/Jul/14 9:10 AM Labels: customer facter logging Priority: Normal Reporter: Charlie Sharpsteen Information logged by Hiera is forwarded to Puppet loggers when Hiera is running as part of a Puppet process. Facter should do the same thing. For Facter, this is especially critical since custom facts contain arbitrary user-written code that can have a variety of side effects — including halting the entire process. Without access to Facter logging info, even when Puppet is running with --debug verbosity, all the user can determine is that the Puppet agent died with doing... something.
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Change By: Charlie Sharpsteen Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-184) Using 'ip addr' over ifconfig
Title: Message Title Eugene Vilensky commented on an issue Re: Using 'ip addr' over ifconfig ifconfig is in the EL7 package 'net-tools' which is not part of the core/minimal install. It would be useful to rely on ip commands instead. Add Comment Facter / FACT-184 Using 'ip addr' over ifconfig # facter /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:85: command not found: /sbin/ifconfig -a /usr/bin/facter:54: command not found: /sbin/ifconfig -a /usr/bin/facter:54: command not found: dnsdomainname /usr/bin/facter:54: command not found: domainname /usr/bin/facter:54: command not found: /sbin/ifconfig architecture => i386 domain => int... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-756) PR (1009): Jul 2014 docs adjustments - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1009): Jul 2014 docs adjustments - nfagerlund kbarber commented: @nfagerlund this looks great! Couple of comments, also - I can't see the changes to the release notes properly, but when I view the rendered diff (its slow) it shows we've lost one level of bullet points in the preview. This might be a github markdown thing. When you're online lets talk about the target for this branch. Add Comment PuppetDB / PDB-756 PR (1009): Jul 2014 docs adjustments - nfagerlund h2. Jul 2014 docs adjustments * Author: Nick Fagerlund <> * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1009 Discussion|https://github.com/puppetlabs/puppetdb/pull/1009] * [Pull Request 1009 File Diff|https://github.com/puppetlabs/puppetdb/pull/1009/files] h2. Pull Request Description Lots of fun stuff! T... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs
Jira (PDB-756) PR (1009): Jul 2014 docs adjustments - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-756 PR (1009): Jul 2014 docs adjustments - nfagerlund Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-757) PR (131): Allow set manage_server in init class - baurmatt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-757 PR (131): Allow set manage_server in init class - baurmatt Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-757) PR (131): Allow set manage_server in init class - baurmatt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-757 PR (131): Allow set manage_server in init class - baurmatt Change By: Kenneth Barber Sprint: 20140702 to 20140716 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-756) PR (1009): Jul 2014 docs adjustments - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-756 PR (1009): Jul 2014 docs adjustments - nfagerlund Change By: Kenneth Barber Sprint: 20140702 to 20140716 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-757) PR (131): Allow set manage_server in init class - baurmatt
Title: Message Title gepetto-bot commented on an issue Re: PR (131): Allow set manage_server in init class - baurmatt Pull request Allow set manage_server in init class has been closed. Add Comment PuppetDB / PDB-757 PR (131): Allow set manage_server in init class - baurmatt h2. Allow set manage_server in init class * Author: Matthias Baur <> * Company: dmc digital media center GmbH * Github ID: [baurmatt|https://github.com/baurmatt] * [Pull Request 131 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/131] * [Pull Request 131 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/131/files] h... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-148) Support multiple backends of the same type
Title: Message Title Merritt commented on an issue Re: Support multiple backends of the same type +1 have the same requirement as above comment. Add Comment Hiera / HI-148 Support multiple backends of the same type It would be great if Hiera could support multiple backends of the same type. Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here: https://github.com/lukebigum/hiera https://github.com/lukebigum/hiera-json And it works with a configuration file like this: ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2926) Print version of failed catalog
Title: Message Title Julien Pivotto created an issue Puppet / PUP-2926 Print version of failed catalog Issue Type: Improvement Affects Versions: 3.6.2 Assignee: Unassigned Created: 11/Jul/14 2:58 AM Priority: Normal Reporter: Julien Pivotto When a catalog compilation fails, it would be grate to get the catalog version Error: Could not retrieve catalog from remote server: Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run could become Error: Could not retrieve catalog version 'Deploy-Fri Jul 11 11:53:56 CEST 2014' from remote server: Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Add Comment
Jira (PDB-757) PR (131): Allow set manage_server in init class - baurmatt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-757 PR (131): Allow set manage_server in init class - baurmatt Issue Type: Task Assignee: Unassigned Created: 11/Jul/14 2:21 AM Labels: github module Priority: Normal Reporter: gepetto-bot Allow set manage_server in init class Author: Matthias Baur <> Company: dmc digital media center GmbH Github ID: baurmatt Pull Request 131 Discussion Pull Request 131 File Diff Pull Request Description Class puppetdb::database::postgresql allows to set the parameter manage_server, but it couldn't be set in the init Class. This is PR fixes this. (webhooks-id: a1c4bbb8cb813ea76512983f6cfdfddc)
