Closed
Bug 1218220
Opened 9 years ago
Closed 9 years ago
split the Boto connection concept from the crashstorage class
Categories
(Socorro :: Backend, task)
Socorro
Backend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lars, Unassigned)
References
Details
we're gonna have to store correlation data in S3, it sure would be handy to have a nicely wrapped Boto connection class to use for this. We've got one, but it is embedded within the BotoS3CrashStorage class. Split it out into a TransactionExecutor compatible ConnectionContext class. That'll give us some nice code reuse. At the same time, this action should in no way have any repercussions on existing uses the BotoS3CrashStorage class. In other words, this action should not affect configuration of any existing App.
Comment 1•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/e6d415a144bff3e49c1d2cd6112777d7a4c2780a bug 1218220 - new boto connection class https://github.com/mozilla/socorro/commit/2d0bb78493f7a1ee10ef459669c9aa7527737bc9 Merge pull request #3061 from twobraids/boto-connections Fixes Bug 1218220 - split the boto connection from the crashstorage class
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•