Closed Bug 932564 Opened 11 years ago Closed 11 years ago

Allow client to be specified in zamboni

Categories

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

Product:
Marketplace Graveyard
Component:
Payments/Refunds
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2013-12-17

People

(Reporter: andy+bugzilla, Assigned: andy+bugzilla)

Details

(Whiteboard: [qa-])

Currently zamboni has quite a lot of this: client.api.bango.... That's not going to work for too long because we need that to be adaptable. For the moment I would suggest something like client.api, or client.api.current looks up what is currently defined as the client in the django config. So there'd be a django config that says SOLITUDE_BACKEND_CLIENT = "bango" or "zippy.reference-paas". That will then translate to the correct lookup and the correct URLs in solitude. With one Django config change we can then swap out the backend in solitude to be something different and all hell breaks loose.
I think we should focus on moving the zamboni API calls down into solitude before we do this, but need to think about the best way to express this.
Assignee: nobody → amckay
Target Milestone: --- → 2013-11-19
Version: 1.5 → 1.4
Priority: -- → P2
CC list accessible: false
Not accessible to reporter
Target Milestone: 2013-11-19 → 2013-12-03
No longer blocks: 917405
Target Milestone: 2013-12-03 → 2013-12-17
I did this in a bunch of different bugs. Including bugs 946006, bug 944799, bug 944769, bug 944540 and so on.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.