Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.4.0

Request #17131 Ability to fetch the logging information per bucket.
Submitted: 2010-02-18 18:05 UTC
From: davidc Assigned: doconnor
Status: Closed Package: Services_Amazon_S3 (version 0.3.1)
PHP Version: 5.3.1 OS: Irrelevant
Roadmaps: (Not assigned)    
Subscription  


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 25 + 48 = ?

 
 [2010-02-18 18:05 UTC] davidc (David Coallier)
Description: ------------ With most of the other libraries now you are usually able to fetch the logging information for the s3 bucket. This is used querying /bucketname?logging Test script: --------------- It's an actual use case of the patch I'm about to attach. <?php $s3 = Services_Amazon_S3::getAccount(ACC, SEC); $buckets = $s3->getBuckets(); foreach ($buckets as $handle => $bucket) { $loggingInfo = $bucket->getLogging(); if ($loggingInfo !== false) { foreach ($loggingInfo as $key => $logNode) { echo 'bucket name: ' . $logNode->nodeName; echo ' bucket log file ' . $logNode->nodeValue; } echo 'no logging enabled for ' . $bucket->name . PHP_EOL; }

Comments

 [2010-02-18 18:14 UTC] davidc (David Coallier)
 [2010-02-18 21:57 UTC] gauthierm (Michael Gauthier)
I think an API somewhat like the ACL API would be more consistent with the rest of Services_Amazon_S3. I started this quickly in SVN, but it is definitely not usable yet: http://svn.php.net/viewvc?view=revision&revision=295240
 [2011-04-25 12:54 UTC] doconnor (Daniel O'Connor)
-Assigned To: +Assigned To: gauthierm
What's left to close this bug?
 [2012-01-25 19:18 UTC] doconnor (Daniel O'Connor)
-Status: Assigned +Status: Closed -Assigned To: gauthierm +Assigned To: doconnor
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.