PuppetDB 1.0.4 is now available for download! This is a bug-fix release of PuppetDB.
Note: Puppet 1.0.3 was not officially released, as additional fixes came in between the time 1.0.3 was tagged and the time we were going to publish release artifacts. PuppetDB 1.0.4 includes all changes from the would-be 1.0.3. # Downloads ============== Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ Available for use with Puppet Enterprise 2.5.1 and later at http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello # Changelog(s) 1.0.4 ========= Many thanks to the following people who contributed patches to this release: * Chris Price Fixes: * (#16554) Fix postgres query for numeric comparisons This commit changes the regex that we are using for numeric comparisons in postgres to a format that is compatible with both 8.4 and 9.1. 1.0.3 ========= NOTE: This version was not officially released, as additional fixes came in between the time we tagged this and the time we were going to publish release artifacts. Many thanks to the following people who contributed patches to this release: * Deepak Giridharagopal * Nick Lewis * Chris Price Fixes: * (#17216) Fix problems with UTF-8 transcoding Certain 5 and 6 byte sequences were being incorrectly transcoded to UTF-8 on Ruby 1.8.x systems. We now do two separate passes, one with iconv and one with our hand-rolled transcoding algorithms. Better safe than sorry! * (#17498) Pretty-print JSON HTTP responses We now output more nicely-formatted JSON when using the PuppetDB HTTP API. * (#17397) DB pool setup fails with numeric username or password This bug happens during construction of the DB connection pool. If the username or password is numeric, when parsing the configuration file they're turned into numbers. When we go to actually create the pool, we get an error because we're passing in numbers when strings are expected. * (#17524) Better logging and response handling for version checks Errors when using the `version` endpoint are now caught, logged at a more appropriate log level, and a reasonable HTTP response code is returned to callers. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
