Fellow humans, This week we triaged PRs for puppetlabs-dhcp, puppetlabs-mysql, and bits of puppetlabs-rabbitmq
puppetlabs-dhcp =============== #32 Remove deprecation warnings for templates and use of concat::setup #36 Add patches from foreman-dhcp * we have a release pending here. puppetlabs-mysql ================ Merged: #545 Update mysqltuner.pl to version 1.3.0 #545 #517 Add Archlinux support (not officially supported) #547 Prevent ERROR 1008 in mysql_database provider (bonus! I merged this one yesterday:) closed: #474 enable removal of mysql::server::backup — closed, we won't support absent, because it's a pain #497 Ignore internal mysql databases when creating a backup (already fixed) #492 parameterize mysqld config_dir (implemented better[?] in #508) #537 Include mysql::server class (this will be fixed by decoupling mysql::db) #542 Adding CentOS rules (duplicate of #544) Needs rebase: #506 added spec test for username validation #405 run mysql_install_db if datadir is set annd mysql database is missing (I tried but gave up) #352 Add timeout parameter to increase for long time running sql imports (I tried but gave up) #440 Some mixup between usin PE and OSS and using puppet vs norm .box files..... Comments: #462 Defined type for managing conf.d entries — this needs a redesign, as suggested. General: We've discussed how to close in on the mariadb support in https://tickets.puppetlabs.com/browse/MODULES-151 I'll be taking a look at this in the next couple of days. puppetlabs-rabbitmq =================== Actually, we didn't touch anything, because we're waiting for #192 This module still needs a https://github.com/puppetlabs/modulesync Tests ===== We're currently working on reducing acceptance tests. In the past we've been quite naïve in writing these. Basically we've been repeating alot of the unit tests by checking if a package is installed or a service is running. Since this is basic puppet functionality, we don't really need to cover that. The other thing that we also want to change is to simplify those tests so we only use the resources available on *all* platforms. The best example for this way forward is puppetlabs-postgresl: https://github.com/puppetlabs/puppetlabs-postgresql/tree/master/spec/acceptance We also discussed to make the Puppetlabs Modules Jenkins publicly accessible. This Jenkins server runs acceptance tests for all supported Operating Systems, how ever it only runs it on merge to master, not yet for all PRs. Baby steps ;) At least that way people can can see how tests are even run at all, and we get a better feel for a module's overal health. Next week we'll do a crawl through Jira again, so if you have any open issues, or any unopened issuese, get started: https://tickets.puppetlabs.com/browse/MODULES So long and thanks for all the <>< -- o/~ i Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641 -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/522390200.7250.1406231826197.JavaMail.zimbra%40brainsware.org. For more options, visit https://groups.google.com/d/optout.
