Jira (PDB-1551) PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker
Title: Message Title gepetto-bot commented on PDB-1551 Re: PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker ajroetker commented: transient ^ 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-4632) puppet agent shows warning messages in red
Title: Message Title Geoff Williams commented on PUP-4632 Re: puppet agent shows warning messages in red Henrik Lindberg are you able to set the background colour and the text colour at the same time? That might be a way to fix it. Users are getting understandably frustrated here, red should be reserved for errors - warnings should definitely be a less jarring colour. This is an important usability issue. 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-1471) Puppetdb 2.3.3 perfomance issue afer upgrading from 1.6
Title: Message Title Akos Hencz commented on PDB-1471 Re: Puppetdb 2.3.3 perfomance issue afer upgrading from 1.6 We have upgraded to the new version, and we saw an improvement in the metrics (notably the enqueue time). However, this comparison is not perfect. After the the performance issues surfaced with 2.3.3, we had to set up a secondary instance of PuppetDB to cope with the load, and directed half our population to the new instance. We have not reverted back to using one instance yet, and we are not sure we will. But even running with half load, the enqueue time improved after the upgrade. 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-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title Igor Galić created an issue Puppet / PUP-4669 Varargs support for (defined) types (and possibly classes) Issue Type: Bug Assignee: Unassigned Components: DSL Created: 2015/05/29 2:09 AM Priority: Normal Reporter: Igor Galić Through roles and profiles, a pattern started to emerge where we write a wrapper define, for convenience, for better naming, both, or other reasons. Example: define http2https_vhost ( $servername= $name, $serveraliases = undef,
Jira (PUP-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title Igor Galić updated an issue Puppet / PUP-4669 Varargs support for (defined) types (and possibly classes) Change By: Igor Galić Issue Type: Bug Improvement 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-4633) User resource fails with UTF-8 comment on 2nd run
Title: Message Title Cédric Barboiron commented on PUP-4633 Re: User resource fails with UTF-8 comment on 2nd run Yep, here it is :https://github.com/puppetlabs/puppet/pull/3977 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-4670) puppet parser validate gives a warning when exported resources are present
Title: Message Title Geoff Williams created an issue Puppet / PUP-4670 puppet parser validate gives a warning when exported resources are present Issue Type: Bug Affects Versions: PUP 3.8.0 Assignee: Eric Sorenson Components: UX Created: 2015/05/29 2:51 AM Environment: $puppet --version 3.8.0 (Puppet Enterprise 3.8.0) Priority: Normal Reporter: Geoff Williams
Jira (PUP-4632) puppet agent shows warning messages in red
Title: Message Title Henrik Lindberg commented on PUP-4632 Re: puppet agent shows warning messages in red Although setting the background color could be a possibility it makes that output look incredibly jarring. Until we find some time to implement bright/dark/off schemes - how about only coloring part of the output? Say only the initial word "Warning" ? Then, even if you cannot really see what it says, you know what a yellow/orange unreadable blob means. I would not mind having warnings in the default color (i.e. black/white or whatever color the console has for normal text). 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-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title
Igor Galić updated an issue
Puppet / PUP-4669
Varargs support for (defined) types (and possibly classes)
Change By:
Igor Galić
Through roles and profiles, a pattern started to emerge where we write a wrapper {{define}}, for convenience, for better naming, both, or other reasons.Example:{code}define http2https_vhost ( $servername= $name, $serveraliases = undef,) { apache::vhost ( "http-${servername}":servername => $servername,serveraliases => $serveraliases,redirect_status => '301',redirect_dest => "https://{servername}/", } apache::vhost ( "https-${servername}":servername => $servername,ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",ssl_cert => "/etc/ssl/certs/${servername}.crt.pem",ssl_key=> "/etc/ssl/private/${servername}.key.pem", }}{code}This is nice and convenient for the most simple of cases. If we need more options from apache::vhost, we have to extend our wrapper profile.Similarly, if apache::vhost changes, and new admins want to use those new options, we (or they!) have to touch our convenience wrappers.We could do a gruesome hack, such as:{code}define http2https_vhost ( $servername= $name, $serveraliases = undef, $options = {},) { apache::vhost ( "http-${servername}":servername => $servername,serveraliases => $serveraliases,redirect_status => '301',redirect_dest => "https://{servername}/", } create_resources('apache::vhost', { "https-${servername}" => $options}, {servername => $servername,ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",ssl_cert => "/etc/ssl/certs/${servername}.crt.pem",ssl_key=> "/etc/ssl/private/${servername}.key.pem", }){code}but the additional indirection through {{$options}} is hard to follow, and with more complex wrappers it's also hard to know where _our options_ start, and where _their options_ end… what is a default, what's being overwritten, etc…I propose we introduce a syntax which helps us create such, or even more powerful wrappers, analogous to clojure's {{&rest}}:{code}define http2https_vhost ( $servername= $name, $serveraliases = undef, &rest,) { apache::vhost ( "http-${servername}":servername => $servername,serveraliases => $serveraliases,redirect_status => '301',redirect_dest => "https://{servername}/", } apache::vhost ( "https-${servername}":servername => $servername, docroot=> "/srv/web/${servername}/htdocs", ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",ssl_cert => "/etc/ssl/certs/${servername}.crt.pem",ssl_key=> "/etc/ssl/private/${servername}.key.pem",&rest, }}{code} note that it Example use:{code}http2https_vhost { 'blag.esotericsystems.at': fallback_resource => '/index.php'{code}It might be useful to _filter_ for specific prefixes,{code}define tc_and_apache_vhost ( $servername= $name, $port = 8080, &tomcat_, &apache_,) { apache::vhost ( "https-${servername}":servername => $servername,ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",ssl_cert => "/etc/ssl/certs/${servername}.crt.pem",ssl_key=> "/etc/ssl/private/${servername}.key.pem",proxy_pass => '/',proxy_dest => "http://localhost:${port}/"&apache_, } tomcat::insta
Jira (PUP-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title
Igor Galić updated an issue
Puppet / PUP-4669
Varargs support for (defined) types (and possibly classes)
Change By:
Igor Galić
Through roles and profiles, a pattern started to emerge where we write a wrapper {{define}}, for convenience, for better naming, both, or other reasons.Example:{code}define http2https_vhost ( $servername= $name, $serveraliases = undef,) { apache::vhost ( "http-${servername}":servername => $servername,serveraliases => $serveraliases,redirect_status => '301',redirect_dest => "https://{servername}/", } apache::vhost ( "https-${servername}":servername => $servername,ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",ssl_cert => "/etc/ssl/certs/${servername}.crt.pem",ssl_key=> "/etc/ssl/private/${servername}.key.pem", }}{code}This is nice and convenient for the most simple of cases. If we need more options from apache::vhost, we have to extend our wrapper profile.Similarly, if apache::vhost changes, and new admins want to use those new options, we (or they!) have to touch our convenience wrappers.We could do a gruesome hack, such as:{code}define http2https_vhost ( $servername= $name, $serveraliases = undef, $options = {},) { apache::vhost ( "http-${servername}":servername => $servername,serveraliases => $serveraliases,redirect_status => '301',redirect_dest => "https://{servername}/", } create_resources('apache::vhost', { "https-${servername}" => $options}, {servername => $servername,ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",ssl_cert => "/etc/ssl/certs/${servername}.crt.pem",ssl_key=> "/etc/ssl/private/${servername}.key.pem", }){code}but the additional indirection through {{$options}} is hard to follow, and with more complex wrappers it's also hard to know where _our options_ start, and where _their options_ end… what is a default, what's being overwritten, etc…I propose we introduce a syntax which helps us create such, or even more powerful wrappers, analogous to clojure's {{&rest}}:{code}define http2https_vhost ( $servername= $name, $serveraliases = undef, &rest,) { apache::vhost ( "http-${servername}":servername => $servername,serveraliases => $serveraliases,redirect_status => '301',redirect_dest => "https://{servername}/", } apache::vhost ( "https-${servername}":servername => $servername,docroot=> "/srv/web/${servername}/htdocs",ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",ssl_cert => "/etc/ssl/certs/${servername}.crt.pem",ssl_key=> "/etc/ssl/private/${servername}.key.pem",&rest, }}{code}Example use:{code}http2https_vhost { 'blag.esotericsystems.at': fallback_resource fallbackresource => '/index.php' } {code} This passes {{fallbackresource}} down to the second {{apache::vhost}}. It might be useful to _filter_ for specific prefixes,{code}define tc_and_apache_vhost ( $servername= $name, $port = 8080, &tomcat_, &apache_,) { apache::vhost ( "https-${servername}":servername => $servername,ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",ssl_cert => "/etc/ssl/certs/${servername}.crt.pem",ssl_key=> "/etc/ssl/private/${servername}.key.pem",proxy_pass =>
Jira (PDB-1557) PR (183): (maint) Change default ssl-host to 0.0.0.0 - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1557 PR (183): (maint) Change default ssl-host to 0.0.0.0 - kbarber Issue Type: Task Assignee: Unassigned Created: 2015/05/29 5:32 AM Labels: github module Priority: Normal Reporter: gepetto-bot (maint) Change default ssl-host to 0.0.0.0 Author: Ken Barber Company: Puppet Labs Inc. Github ID: kbarber Pull Request 183 Discussion Pull Request 183 File Diff Pull Request Description This was changes in the package, but never reflected in the module. Signed-off-by: Ken Barber (webhooks-id: 96bbc82acb864753c
Jira (PDB-1557) PR (183): (maint) Change default ssl-host to 0.0.0.0 - kbarber
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-1557 PR (183): (maint) Change default ssl-host to 0.0.0.0 - kbarber Change By: Kenneth Barber Component/s: Module Assignee: Kenneth Barber Sprint: PuppetDB 2015-06-03 Story Points: 1 Scope Change Reason: User found this on puppet-users forum, so fixing since its trivial Scope Change Category: Found Fix Version/s: PDB module-5.0.0 Add Comment
Jira (PUP-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title
Rob Nelson commented on PUP-4669
Re: Varargs support for (defined) types (and possibly classes)
What about using hash keys to split the &rest?
http2https_vhost { 'blag.esotericsystems.at':
apache => {
fallbackresource => '/index.php',
},
tomcat => {
tomcatsetting => 'whatever',
}
}
Also, how would you expect the closure to handle any duplicated settings, such as setting docroot in &rest when the defined type already specifies a root? I would expect the &rest options to win out, but it should be specified that is the case if so.
Jira (PUP-4632) puppet agent shows warning messages in red
Title: Message Title Geoff Williams commented on PUP-4632 Re: puppet agent shows warning messages in red I think both of those ideas would be good compromises. Maybe even bold text instead of red text for warnings - in the regular text colour - can that be done? 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-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title
Henrik Lindberg commented on PUP-4669
Re: Varargs support for (defined) types (and possibly classes)
This rapidly snowballs into all sorts of corner cases (and this was the reason for not implementing support for "varargs" in the "pass arguments by name"-scheme used by defines and classes - e.g. merge or not, flatten or not, make unique or not, does data binding apply, if so for everything, or for keyed parts. If ignoring all such cases the created instrument is most likely to be too blunt, and if implementing everything it becomes yet another swiss army knife and more magic operators/punctuation.
How about a simpler mechanism where varargs simply accumulate into a single hash, and that it is then up to the implementor to slice/transform that with the rules that are required?
This:
foo { title:
attr => val,
&prefix_,
}
can be achieved with ($captured is the "varargs" parameter):
foo { title:
attr => val,
* => $captured.filter |$x| { $x =~ 'prefix_'}
Jira (PUP-4632) puppet agent shows warning messages in red
Title: Message Title Henrik Lindberg commented on PUP-4632 Re: puppet agent shows warning messages in red Not sure about 'bold' - would have to be investigated. Other ideas is to use something reminiscent of an icon: e.g. [X], [!], [?], and that those are in color, rest in black. (Less wordy - now we often see "Error: SomeError" or similar - or use emoji icons even?). This because icons also work for those that have red/green color deficiencies. The usability of these suggestions (+ I am sure there are other ways), should really be put to UX to test them out w.r.t readability, signal/noise ratio, dark/bright background user preferences, what works for the "color-blind", etc. etc. 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-4670) puppet parser validate gives a warning when exported resources are present
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4670 puppet parser validate gives a warning when exported resources are present Change By: Henrik Lindberg Issue Type: Bug Improvement 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-4670) puppet parser validate gives a warning when exported resources are present
Title: Message Title Henrik Lindberg commented on PUP-4670 Re: puppet parser validate gives a warning when exported resources are present I believe we have a ticket for this somewhere - these warnings should not be issued at neither parsing nor validation time - they are pure runtime errors. It has been this way since Pterodactyls where common... 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera defaults to reflect current best practices Mark Butcher Can you update the PR to reflect the changes as per the description? 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-1551) PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker
Title: Message Title gepetto-bot commented on PDB-1551 Re: PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker Pull request (maint) Remove `paged_results.*` wrapper around generated sql has been 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 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-1555) PR (182): (maint) Allow database_validation to be false - ajroetker
Title: Message Title gepetto-bot commented on PDB-1555 Re: PR (182): (maint) Allow database_validation to be false - ajroetker kbarber commented: @ajroetker probably target this at stable, in case we need to release it. 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-1555) PR (182): (maint) Allow database_validation to be false - ajroetker
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1555 PR (182): (maint) Allow database_validation to be false - ajroetker Change By: Kenneth Barber Affects Version/s: PDB module-4.2.1 Fix Version/s: PDB 3.0.0 Fix Version/s: PDB module-4.3.0 Issue Type: Task Bug 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-4632) puppet agent shows warning messages in red
Title: Message Title Kylo Ginsberg commented on PUP-4632 Re: puppet agent shows warning messages in red This is a dup of PUP-3838 , which was fixed in 4.0. Closing, but some of the follow-on enhancement ideas discussed here could be rolled up into another ticket? 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-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title
Igor Galić commented on PUP-4669
Re: Varargs support for (defined) types (and possibly classes)
Henrik Lindberg, how would the "easy" case look of my above &rest look like now?
define http2https_vhost (
$servername= $name,
Optional[Array[Strings]] $serveraliases,
Struct[{ /^/ => Any }] = *$rest,
) {
...
apache::vhost ( "https-${servername}":
servername => $servername,
docroot=> "/srv/web/${servername}/htdocs",
ssl_ca => "/etc/ssl/certs/${servername}s.ca.pem",
Jira (PUP-4632) puppet agent shows warning messages in red
Title: Message Title Henrik Lindberg commented on PUP-4632 Re: puppet agent shows warning messages in red Doh, and damned - so now it is unreadable for a different group of users 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-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title
Henrik Lindberg commented on PUP-4669
Re: Varargs support for (defined) types (and possibly classes)
Baically yes. We could also support a Hash type for cases where you do not want key/type patter/name checking for the varargs parameter:
define http2https_vhost (
$servername= $name,
Optional[Array[String]] $serveraliases,
Hash *$rest,
) {
... # same as in your example
}
Add Comment
Jira (PUP-3053) SSL configuration with intermediate CA
Title: Message Title Celia Cottle assigned an issue to Josh Cooper Puppet / PUP-3053 SSL configuration with intermediate CA Change By: Celia Cottle Assignee: Kaitlin Carter Josh Cooper 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-1557) PR (183): (maint) Change default ssl-host to 0.0.0.0 - kbarber
Title: Message Title gepetto-bot commented on PDB-1557 Re: PR (183): (maint) Change default ssl-host to 0.0.0.0 - kbarber ajroetker commented: :+1: 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-1555) PR (182): (maint) Allow database_validation to be false - ajroetker
Title: Message Title gepetto-bot commented on PDB-1555 Re: PR (182): (maint) Allow database_validation to be false - ajroetker ajroetker commented: will do 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-1558) PR (184): (maint) Allow database_validation to be false - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1558 PR (184): (maint) Allow database_validation to be false - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/05/29 8:46 AM Labels: github module Priority: Normal Reporter: gepetto-bot (maint) Allow database_validation to be false Author: Andrew Roetker <> Company: Puppet Labs Github ID: ajroetker Pull Request 184 Discussion Pull Request 184 File Diff Pull Request Description This commit fixes a bug where if a user tried to turn off database validation there would be a `before` statement requiring an absent validation resource. (webh
Jira (PDB-1555) PR (182): (maint) Allow database_validation to be false - ajroetker
Title: Message Title gepetto-bot commented on PDB-1555 Re: PR (182): (maint) Allow database_validation to be false - ajroetker Pull request (maint) Allow database_validation to be false has been 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 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-1558) PR (184): (maint) Allow database_validation to be false - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1558 PR (184): (maint) Allow database_validation to be false - ajroetker Change By: AJ Roetker Sprint: PuppetDB 2015-06-03 Story Points: 1 Scope Change Reason: Quick fix for someone on puppet-users Scope Change Category: Adopted Fix Version/s: PDB 3.0.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 unsub
Jira (PDB-1558) PR (184): (maint) Allow database_validation to be false - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1558 PR (184): (maint) Allow database_validation to be false - ajroetker Change By: AJ Roetker Issue Type: Task Bug 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-1537) Add redirect from `/` to `/pdb/dashboard/index.html` if PuppetDB is alone in JVM
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1537 Add redirect from `/` to `/pdb/dashboard/index.html` if PuppetDB is alone in JVM Change By: Wyatt Alt Scope Change Category: Adopted 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-1345) Add puppetdb-sync unit test feedback to puppetdb travis-ci
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1345 Add puppetdb-sync unit test feedback to puppetdb travis-ci Change By: AJ Roetker Fix Version/s: PDB 3.0.0 Fix Version/s: PDB 3.1.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 (PDB-1516) shutdown sometimes stalls causing failure on restart
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1516 shutdown sometimes stalls causing failure on restart Change By: Kenneth Barber Story Points: 2 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-1125) PuppetDB terminus fetches unstructured facts instead of structured
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1125 PuppetDB terminus fetches unstructured facts instead of structured Change By: Kenneth Barber Story Points: 0 2 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-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Branan Riley commented on PUP-3774 Re: puppet fails to manipulate user's group membership if group name has space in it OK, I think I see what's going on here. When group membership is set to minimal, Puppet actually fetches the current groups and does a set union on the requested and current sets, then passes that to the provider as the complete set of groups. This logic should probablyi happen in the individual providers themselves, to allow them to either ensure the whole list or add groups piecemeal (depending on what makes sense for that provider/platform). This would allow the useradd provider to do something more like what the reporter did, which is simply adding a user to a group. I'm currently digging through the layers of metaprogramming that are the user providers to figure out where this logic is happening and how I can beat it into the form I want. 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-4635) Cannot install packages without membership to any group with pacman provider
Title: Message Title Peter Huene updated an issue Puppet / PUP-4635 Cannot install packages without membership to any group with pacman provider Change By: Peter Huene Sprint: Client 2015-06-10 Scope Change Reason: Adopted due to community impact Scope Change Category: Adopted 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-1516) shutdown sometimes stalls causing failure on restart
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1516 shutdown sometimes stalls causing failure on restart Change By: Wyatt Alt Sprint: PuppetDB 2015-06- 17 03 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-1516) shutdown sometimes stalls causing failure on restart
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1516 shutdown sometimes stalls causing failure on restart Change By: Wyatt Alt Assignee: Wyatt Alt 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-4632) puppet agent shows warning messages in red
Title: Message Title Kylo Ginsberg commented on PUP-4632 Re: puppet agent shows warning messages in red I have no hard data other than walking by people's desks and seeing CLI demo videos, but based on that anecdoatal data, black background is most common. I do think distinguishing warnings from errors makes a lot of sense UX-wise. Also, color profiles would be a nice enhancement (or turning off color altogether). Maybe we should ticket those ideas. 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-4671) inventory beaker helpers in acceptance/lib
Title: Message Title Eric Thompson created an issue Puppet / PUP-4671 inventory beaker helpers in acceptance/lib Issue Type: Task Assignee: Eric Thompson Components: QA Created: 2015/05/29 10:56 AM Priority: Normal Reporter: Eric Thompson beaker test helpers are spread across various projects and not well defined nor tested nor implemented. we need to take an inventory to see usage so we can define what should be brought back into beaker or a separate gem or beaker plugin. candidates include anything useful for other projects (methods or classes that might be repeated across projects). separation from beaker candidates include any methods or data that are related to a product under test, or puppetlabs infrastructure specific. inventory (ping eric if the spreadsheet is unclear or how to find these helpers and their usage is unclear): https://docs.google.com/spreadsheets/d/1F5sE2ruX388k-hiCCiH063lRBoUO556eFg93YD59-bo/edit#gid=0 Add Comment
Jira (PUP-4672) inventory beaker helpers in acceptance
Title: Message Title Eric Thompson created an issue Puppet / PUP-4672 inventory beaker helpers in acceptance Issue Type: Task Assignee: Eric Thompson Components: QA Created: 2015/05/29 10:59 AM Priority: Normal Reporter: Eric Thompson beaker test helpers are spread across various projects and not well defined nor tested nor implemented. we need to take an inventory to see usage so we can define what should be brought back into beaker or a separate gem or beaker plugin. candidates include anything useful for other projects (methods or classes that might be repeated across projects). separation from beaker candidates include any methods or data that are related to a product under test, or puppetlabs infrastructure specific. inventory (ping eric if the spreadsheet is unclear or how to find these helpers and their usage is unclear): https://docs.google.com/spreadsheets/d/1F5sE2ruX388k-hiCCiH063lRBoUO556eFg93YD59-bo/edit#gid=0 Add Comment
Jira (PUP-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3480 Puppet does not have Python 3 package provider (pip3) Change By: Kurt Wall Assignee: QA Kurt Wall 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Nicholas Fagerlund commented on HI-374
Re: Update hiera defaults to reflect current best practices
Ping. Since Hiera 2 only ships with Puppet versions that have $trusted enabled by default, let's stop using the insecure $clientcert variable. The hierarchy should include
certname/%{::trusted.certname}
instead.
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-3166) Debian service provider on docker with insserv (dep boot sequencing)
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3166 Debian service provider on docker with insserv (dep boot sequencing) Change By: Kurt Wall Assignee: QA Kurt Wall 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-1559) Complete connection pool handling in jdbc-util
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1559 Complete connection pool handling in jdbc-util Issue Type: New Feature Assignee: Kenneth Barber Created: 2015/05/29 11:58 AM Priority: Normal Reporter: Kenneth Barber 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-4668) cannot create a define named something that starts with 'class'
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4668 cannot create a define named something that starts with 'class' Change By: Eric Thompson QA Risk Severity: Medium QA Risk Probability: Low QA Risk Severity Reason: work arounds exist QA Highest Test Level: Unit 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-4668) cannot create a define named something that starts with 'class'
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4668 cannot create a define named something that starts with 'class' Change By: Eric Thompson QA Risk Assessment: Medium 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-2638) Missing dependent directory from Puppet Agent install causes issues with resource graphing
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install causes issues with resource graphing Change By: Eric Thompson QA Risk Severity: Medium QA Risk Probability: Medium QA Risk Severity Reason: workarounds QA Risk Assessment: Medium QA Risk Probability Reason: graphing turned on; no agent runs; apply fails QA Highest Test Level: Acceptance QA Contact: Erik Dasher Eric Thompson Add Comment
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Sorenson commented on HI-374 Re: Update hiera defaults to reflect current best practices Ahh good catch Nicholas Fagerlund – Nick Walker Gary Larizza what do you think about that ^^^ 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-4671) inventory beaker helpers in acceptance/lib
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4671 inventory beaker helpers in acceptance/lib Change By: Eric Thompson QA Status: Reviewed 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-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Branan Riley commented on PUP-3774 Re: puppet fails to manipulate user's group membership if group name has space in it Managed to do this without having to move around a ton of logic, but it involves duplicating some set operations and I think also duplicates some data fetches currently. I should be able to cache the data fetches, but I'm not sure how nasty the set munging is going to be in the real world. 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-4666) build_ignore_module_file fails if '/tmp/test' already exists
Title: Message Title Jeremy Barlow commented on PUP-4666 Re: build_ignore_module_file fails if '/tmp/test' already exists Was merged to the Puppet stable branch at 90cb8f1c548842923bca917fa04f73f00f9a8ed4. AIO Agent / Stable pipeline seems to still be passing okay with this change: https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Stable/view/Puppet/job/platform_aio-puppet_pkg-promote_stable/78/ We also picked this change into the master branch Puppet Server acceptance test pipeline, and the test is now passing there as well: https://jenkins.puppetlabs.com/view/Puppet%20Server/view/All/job/platform_puppet-server_integration-system_no-conditional_full-master/73/ Closing since I don't think any further QA review is needed. 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-1559) Complete connection pool handling in jdbc-util
Title: Message Title Kenneth Barber commented on PDB-1559 Re: Complete connection pool handling in jdbc-util The PR is here: https://github.com/puppetlabs/jdbc-util/pull/10 We need to follow up on these comments, get the patch merged, get a release of jdbc-utils and then start to get some projects to move to this. 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-1559) Complete connection pool handling in jdbc-util
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1559 Complete connection pool handling in jdbc-util Change By: Kenneth Barber This is a follow up on PDB-1448, raw notes are here: https://docs.google.com/document/d/1gqBdMyMMZAhCb3kJpSP3sPUgJ9IMKRmPHbdAznGNOZc/edit 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Nick Walker commented on HI-374 Re: Update hiera defaults to reflect current best practices Seems reasonable to me since this will only affect new users. I had a thought that for users upgrading their certs would have been generated before trusted facts existed and that might cause an issue but that should be a non-issue since this is for new users only (existing users keep their existing hiera.yaml). I don't know much about trusted facts but assuming it "just works" then I'm for it. I googled "trusted facts hiera" and couldn't find anything on the subject. 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-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Henrik Lindberg commented on PUP-4665 Re: Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Merged to 3.x at 9209794 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-2400) Add acceptance tests for mount type
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-2400 Add acceptance tests for mount type Change By: John Duarte Assignee: Kurt Wall John Duarte 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-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Henrik Lindberg commented on PUP-4665 Re: Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Merged cleanly to stable and master 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Thompson updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Eric Thompson QA Risk Severity: Low QA Risk Probability: Medium QA Risk Severity Reason: just defaults. less friction for users QA Risk Assessment: Medium QA Risk Assessment Reason: qa validate for another check, no way to automate? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed
Jira (FACT-1011) Docs prep for facter 3
Title: Message Title Eric Thompson updated an issue Facter / FACT-1011 Docs prep for facter 3 Change By: Eric Thompson QA Status: Reviewed 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4638 Rename module to puppetlabs-puppet_agent Change By: Eric Thompson QA Status: Reviewed 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4638 Rename module to puppetlabs-puppet_agent Change By: Eric Thompson QA Risk Assessment: Low 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-4431) Service with 'hasstatus => false' fails
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4431 Service with 'hasstatus => false' fails Change By: Eric Thompson Assignee: QA Eric Thompson 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera defaults to reflect current best practices Nick Walker Try searching for "structured facts hiera", which works the same way, only starting from $facts instead of $trusted. 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-4632) puppet agent shows warning messages in red
Title: Message Title Henrik Lindberg commented on PUP-4632 Re: puppet agent shows warning messages in red hm, so PUP-3838 also made it inconsistent with puppet apply - not all logging uses the symbolic colors - wild west... 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-1021) Custom facts that "require 'facter'" cannot be evaluated from command line facter
Title: Message Title Peter Huene created an issue Facter / FACT-1021 Custom facts that "require 'facter'" cannot be evaluated from command line facter Issue Type: Bug Affects Versions: FACT 3.0.0 Assignee: Peter Huene Created: 2015/05/29 1:40 PM Fix Versions: FACT 3.0.0 Priority: Normal Reporter: Peter Huene Custom fact file foo/foo.rb: require 'facter' Facter.add(:foo) do
Jira (PUP-4662) EPP template can't explicitly access top scope variables if there's no node definition in the scope chain
Title: Message Title Henrik Lindberg commented on PUP-4662 Re: EPP template can't explicitly access top scope variables if there's no node definition in the scope chain This is caused by a general problem in the implementation of Scope (is there no end to how much grief this implementation will cause?) as a lookup of a fully qualified variable from top scope ends up looking up the top scope and then getting it from there. Since local and ephemeral scopes mutate the scope's state - when doing this from within a local scope, it is simply not possible to look up from the actual top scope!!! The number of corner cases and if/then/else spaghetti in the implementation is depressing - this adds yet another case. The reason it works from within node scope is that it is not "the top scope". 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-1560) PR (1427): (packaging)Update paths to AIO layout - shrug
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1560 PR (1427): (packaging)Update paths to AIO layout - shrug Issue Type: Task Assignee: Unassigned Created: 2015/05/29 2:23 PM Labels: github Priority: Normal Reporter: gepetto-bot (packaging)Update paths to AIO layout Author: Rob Braden <> Company: Puppet Labs Github ID: shrug Pull Request 1427 Discussion Pull Request 1427 File Diff Pull Request Description Update to ezbake 0.3.7 and associated path changes to reflect the layout specified in https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md. (webhooks-id: 7e5a16a47a27d
Jira (PDB-1560) PR (1427): (packaging)Update paths to AIO layout - shrug
Title: Message Title gepetto-bot commented on PDB-1560 Re: PR (1427): (packaging)Update paths to AIO layout - shrug haus commented: @shrug this all looks good to me. I have that 1 comment, but it shouldn't block merging. 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-3166) Debian service provider on docker with insserv (dep boot sequencing)
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-3166 Debian service provider on docker with insserv (dep boot sequencing) Change By: Kurt Wall Assignee: Kurt Wall 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-1561) Split Command into it's own API
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-1561 Split Command into it's own API Issue Type: Improvement Assignee: Unassigned Created: 2015/05/29 2:48 PM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: AJ Roetker Command submission and endpoint should be split off into it's own service at `/pdb/cmd` Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1560) PR (1427): (packaging)Update paths to AIO layout - shrug
Title: Message Title gepetto-bot commented on PDB-1560 Re: PR (1427): (packaging)Update paths to AIO layout - shrug pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1338/ 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-1562) Split Version and Server-time into it's own API
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-1562 Split Version and Server-time into it's own API Issue Type: Improvement Assignee: Unassigned Created: 2015/05/29 2:50 PM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: AJ Roetker The version and server-time endpoints deserve their own `/pdb/meta` API Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1035) Our module won't work with PDB 3.0.0 once released, as it has a new module package name
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1035 Our module won't work with PDB 3.0.0 once released, as it has a new module package name Change By: AJ Roetker Sprint: PuppetDB 2015-01-28, PuppetDB 2015-06- 17 03 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-967) Add AIX operating_system_resolver.cc
Title: Message Title William Hopper commented on FACT-967 Re: Add AIX operating_system_resolver.cc Something like this is fairly fast (up from 0.087s to 0.139s): https://gist.github.com/whopper/44591637f9f4ab749be2 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-1035) Our module won't work with PDB 3.0.0 once released, as it has a new module package name
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1035 Our module won't work with PDB 3.0.0 once released, as it has a new module package name Change By: AJ Roetker In PuppetDB 3.0.0 the terminus package name is now `puppetdb-termini` but our module still uses the old standard. Need to figure out what to do here. The override is to use `terminus_package` parameter in one of the classes, but this seems less optimal for long term use. This ticket also includes setting the defaults for PDB 3.0.0, such as the test_url to the new `/pdb/meta/v1/version` endpoint. 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-1516) shutdown sometimes stalls causing failure on restart
Title: Message Title Wyatt Alt commented on PDB-1516 Re: shutdown sometimes stalls causing failure on restart I've spent the better part of the day trying to reproduce this, with no luck. My guess is that this was my own user error or that it went away with 0e02a04b21c77b89cae9509170281a1c2b867bb2. Closing the investigation. 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Justin Stoller commented on PUP-4638 Re: Rename module to puppetlabs-puppet_agent pipeline deployed here: https://jenkins-modules.puppetlabs.com/view/4.%20cross%20platform/view/puppet_agent/view/master/ just ping me and I'll enable it (its disabled so it isn't red on the radiator) 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-1560) PR (1427): (packaging)Update paths to AIO layout - shrug
Title: Message Title gepetto-bot commented on PDB-1560 Re: PR (1427): (packaging)Update paths to AIO layout - shrug pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1339/ 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-1548) PR (1420): (maint) Cleanup benchmarking tool clojure syntax - ajroetker
Title: Message Title gepetto-bot commented on PDB-1548 Re: PR (1420): (maint) Cleanup benchmarking tool clojure syntax - ajroetker mullr commented: tested locally, lgtm 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Kylo Ginsberg commented on PUP-4638 Re: Rename module to puppetlabs-puppet_agent Justin Stoller I renamed the repo so you can enable the new pipeline and disable the old one. 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-1556) PR (1425): (maint) Remove unneccesary querying macro to improve streaming syntax - ajroetker
Title: Message Title gepetto-bot commented on PDB-1556 Re: PR (1425): (maint) Remove unneccesary querying macro to improve streaming syntax - ajroetker mullr commented: generally looks ok, just some minor comments 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-4431) Service with 'hasstatus => false' fails
Title: Message Title
Eric Thompson commented on PUP-4431
Re: Service with 'hasstatus => false' fails
validated on debian7 at SHA: d26c029
[root@gx7rlphwpuklmle ~]# puppet apply hasstatus.pp
Notice: Compiled catalog for gx7rlphwpuklmle.delivery.puppetlabs.net in environment production in 0.54 seconds
Notice: /Stage[main]/Main/Service[mynetconsole]/ensure: ensure changed 'stopped' to 'running'
Notice: Applied catalog in 0.20 seconds
[root@gx7rlphwpuklmle ~]# cat hasstatus.pp
service { "mynetconsole":
ensure => running,
enable => true,
hasstatus => false,
}
Jira (PDB-1550) PR (1422): (maint) don't activate the node when it's already active - wkalt
Title: Message Title gepetto-bot commented on PDB-1550 Re: PR (1422): (maint) don't activate the node when it's already active - wkalt mullr commented: I'm :+1: on this in master, but we decided to skip it in stable. 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-4662) EPP template can't explicitly access top scope variables if there's no node definition in the scope chain
Title: Message Title Henrik Lindberg commented on PUP-4662 Re: EPP template can't explicitly access top scope variables if there's no node definition in the scope chain Further, it was not detected because the test that should test this particular case was flawed! 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-4648) Problem of indentation with epp()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4648 Problem of indentation with epp() Change By: Henrik Lindberg Sprint: Client Language 2015- 07 06 - 08 24 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Kylo Ginsberg commented on PUP-4638 Re: Rename module to puppetlabs-puppet_agent I renamed the pipeline and it ran green through the new pipeline that Justin just set up. I now have a PR for the renames within the repo. 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-4648) Problem of indentation with epp()
Title: Message Title Henrik Lindberg commented on PUP-4648 Re: Problem of indentation with epp() The problem is caused by the first -%> being handled wrong - it ends up being sticky. Removing the - makes the indentation work (it adds a blank line though, so it is not a work around). 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-4648) Problem of indentation with epp()
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4648
Problem of indentation with epp()
Change By:
Henrik Lindberg
Comment:
The problem is caused by the first {{\-%>}} being handled wrong - it ends up being sticky. Removing the {{-}} makes the indentation work (it adds a blank line though, so it is not a work around).
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-1563) PR (1428): Ticket/pdb 1561/master/split command api - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1563 PR (1428): Ticket/pdb 1561/master/split command api - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/05/29 5:46 PM Labels: github Priority: Normal Reporter: gepetto-bot Ticket/pdb 1561/master/split command api Author: Andrew Roetker <> Company: Puppet Labs Github ID: ajroetker Pull Request 1428 Discussion Pull Request 1428 File Diff Pull Request Description Split out Command API into it's own TK service. (webhooks-id: 54c5c743272609d79ff6665ce1d18bb8)
Jira (PDB-1563) PR (1428): Ticket/pdb 1561/master/split command api - ajroetker
Title: Message Title gepetto-bot commented on PDB-1563 Re: PR (1428): Ticket/pdb 1561/master/split command api - ajroetker ajroetker commented: @mullr wanna take another look? 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-4673) Pip installs from behind proxy can't ensure=>latest
Title: Message Title Spencer Krum created an issue Puppet / PUP-4673 Pip installs from behind proxy can't ensure=>latest Issue Type: Bug Assignee: Unassigned Created: 2015/05/29 6:15 PM Environment: behind http proxy Priority: Normal Reporter: Spencer Krum The pip package provider can ensure => version but can't ensure latest when using a proxy. https://github.com/puppetlabs/puppet/pull/3984 (venv)krum@ftctstories01g:~$ env| grep proxy http_proxy=http://web-proxy.houston.hp.com:8080 HTTPS_PROXY=http://web-proxy.houston.hp.com:8080 https_proxy=http://web-proxy.houston.hp.com:8080 HTTP_PROXY=http://web-proxy.houston.hp.com:8080 (venv)krum@ftctstories01g:~$ puppet --version 3.7.4 (venv)krum@ftctstories01g:~$ ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] (venv)krum@ftctstories01g:~$ gem --version 1.8.15 $ puppet resource package gear provider=pip ensure=latest --debug --trace Debug: Runtime environment: ruby_version=1.8.7, run_mode=user, puppet_version=3.7.4 Debug: Puppet::Type::Package::ProviderNim: file /usr/bin/lslpp does not exist Debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist Debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not exist Debug: Puppet::Type::Package::ProviderSun: file /usr/bin/pkginfo does not exist Debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_info does not exist Debug: Puppet::Type::Package::ProviderPacman: file /usr/bin/pacman does not exist Debug: Puppet::Type::Package::ProviderZyp
Jira (PDB-1563) PR (1428): Ticket/pdb 1561/master/split command api - ajroetker
Title: Message Title gepetto-bot commented on PDB-1563 Re: PR (1428): Ticket/pdb 1561/master/split command api - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1340/ 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Justin Stoller commented on PUP-4638 Re: Rename module to puppetlabs-puppet_agent You renamed the pipeline? I assume you mean repo. Please let me know if you manually changed the pipelines. I've deleted the old pipeline now that we've seen the new one go green end to end. 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Kylo Ginsberg commented on PUP-4638 Re: Rename module to puppetlabs-puppet_agent Yep that was an error. I fixed the comment. 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.
