Closed
Bug 886445
Opened 12 years ago
Closed 12 years ago
Upload log to S3
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-06-27
People
(Reporter: andy+bugzilla, Assigned: andy+bugzilla)
Details
(Whiteboard: [qa-])
In bug 863416 we wrote a payments logs. After chatting to oremj, he'd like it pushed to S3 by solitude once complete. This means adding in boto as a solitude dependency and then adding the code to push in that cron.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → amckay
Priority: -- → P2
Target Milestone: --- → 2013-06-27
Assignee | ||
Comment 1•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 2•12 years ago
|
||
it would not be a bad idea to encrypt this log since it's going on S3. Even though it doesn't contain personal info, it contains opaque user hashes which can allow someone to create a purchase history.
Comment 3•12 years ago
|
||
(In reply to Kumar McMillan [:kumar] from comment #2)
> it would not be a bad idea to encrypt this log since it's going on S3. Even
> though it doesn't contain personal info, it contains opaque user hashes
> which can allow someone to create a purchase history.
has this been addressed?
Updated•12 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•