On Thu, 17 Feb 2011, Nigel Kersten wrote:
https://projects.puppetlabs.com/issues/6353
Our old behavior was that when files were backed up to a filebucket,
we also wrote out the path information to the 'paths' file in the
checksum directory.
Do people actually use this functionality? Our
Hi,
we've actually built tools around this behaviour. Scheduled puppet
resources can put files in a central bucket, and the data is collected
by mixing mtime and paths information of the bucketed files.
Granted, that's probably not what the bucket was conceived for, but it
sure is convenient
I care a lot and had thought that the path would eventually be the main
key for retrieving files, with the checksum being sort of like a
revision, with some extra metadata when you interfaces with the
filebucket...
On 02/17/2011 03:46 PM, Nigel Kersten wrote:
On Thu, Feb 17, 2011 at 12:48 PM, Joe McDonagh
joseph.e.mcdon...@gmail.com wrote:
I care a lot and had thought that the path would eventually be the main key
for retrieving files, with the checksum being sort of like a revision, with
some extra metadata when you interfaces with the
On 02/17/2011 03:55 PM, Nigel Kersten wrote:
On Thu, Feb 17, 2011 at 12:48 PM, Joe McDonagh
joseph.e.mcdon...@gmail.com wrote:
I care a lot and had thought that the path would eventually be the main key
for retrieving files, with the checksum being sort of like a revision, with
some extra
On Thu, Feb 17, 2011 at 3:55 PM, Nigel Kersten ni...@puppetlabs.com wrote:
ok. So it's unacceptable for you to refer to logs or reports to get
the checksum for a given replacement and then restore the file that
It's really damn fiddly :-)
As a git guts hacker, I appreciate that puppet stores
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I always expected to be able to access the values by path.
Having to recall a hash from a log is pretty much unrealistic without tools to
help you map the hash to the file at a later date.
I.e. Puppet supplied log parsers/data map store tools,
