Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Announce: PuppetDB 1.0.1 Available
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Moses Mendoza  
View profile  
 More options Oct 10 2012, 5:31 pm
From: Moses Mendoza <mo...@puppetlabs.com>
Date: Wed, 10 Oct 2012 14:31:19 -0700
Local: Wed, Oct 10 2012 5:31 pm
Subject: Announce: PuppetDB 1.0.1 Available
PuppetDB 1.0.1 is now available for download! This is a bug-fix
release of PuppetDB.

# 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

# 1.0.1 Changelog
==============
Many thanks to the following people who contributed patches to this release:
Deepak Giridharagopal
Nick Lewis
Matthaus Litteken
Chris Price

Fixes:
(#16180) Properly handle edges between exported resources

This was previously failing when an edge referred to an exported
resource which was also collected, because it was incorrectly assuming
collected resources would always be marked as NOT exported. However,
in the case of a node collecting a resource which it also exports, the
resource is still marked exported. In that case, it can be
distinguished from a purely exported resource by whether it's virtual.
Purely virtual, non-exported resources never appear in the catalog.

Virtual, exported resources are not collected, whereas non-virtual,
exported resources are. The former will eventually be removed from the
catalog before being sent to the agent, and thus aren't eligible for
participation in a relationship. We now check whether the resource is
virtual rather than exported, for correct behavior.

(#16535) Properly find edges that point at an exec by an alias

During namevar aliasing, we end up changing the :alias parameter to
'alias' and using that for the duration (to distinguish "our" aliases
form the "original" aliases). However, in the case of exec, we were
bailing out early because execs aren't isomorphic, and not adding
'alias'. Now we will always change :alias to 'alias', and just won't
add the namevar alias for execs.

(#16407) Handle trailing slashes when creating edges for file resources

We were failing to create relationships (edges) to File resources if
the relationship was specified with a different number of trailing
slashes in the title than the title of the original resource.

(#16652) Replace dir with specific files for terminus package

Previously, the files section claimed ownership of Puppet's libdir,
which confuses rpm when both packages are installed. This commit
breaks out all of the files and only owns one directory, which clearly
belongs to puppetdb. This will allow rpm to correctly identify files
which belong to puppet vs puppetdb-terminus.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »