Closed Bug 801108 Opened 12 years ago Closed 12 years ago

Set up database for webpay (users, transactions, secret keys)

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED
2012-10-18

People

(Reporter: kumar, Assigned: kumar)

References

Details

(Whiteboard: [qa-])

Make webpay independent from Zamboni models and seed a database with: - users (based on Persona assertions) - transactions - secret keys Some of this may go into Solitude but we can factor that out later. More info: https://etherpad.mozilla.org/webpay-brainstorm
Assignee: nobody → kumar.mcmillan
Blocks: 794651
Priority: -- → P1
Target Milestone: --- → 2012-10-18
See also bug 797991. Also, transactions with Bango have to occur in solitude anyway...
I'd like to try a first iteration with everything in webpay then move them out. That way we can get something working without having to spend extra time designing and deploying the solitude services.
I mainly want to avoid what happened last time where we built things using solitude then had to throw them away. I was thinking of using this bug to try out a self-contained database approach to see if still feels like a good fit and to see if we hit any blockers.
I just want to avoid what happened last time where we had a bunch of "if solitude" waffle flags everywhere and thinking about migrations etc. Whatever works, I'm easy.
We're still discussing how much we'll move to solitude (maybe all?) but this should serve as a basic guide https://github.com/mozilla/webpay/commit/0a7bda588332a6b0a96749adaa5b1172b6265de9
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.