Closed Bug 1115184 Opened 10 years ago Closed 8 years ago

Setup trunion in docker

Categories

(Marketplace Graveyard :: Integration, defect, P4)

Product:
Marketplace Graveyard
Component:
Integration
Version:
Avenir
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: andy+bugzilla, Assigned: rtilder)

References

Details

We currently fake out trunion for local devs and inside docker. Would be nice if we had a trunion running so we can test out how trunion interacts and catch surprises before they hit prod.

https://github.com/mozilla/marketplace-env
Priority: -- → P4
Blocks: 1118050
Depends on: 939958
Assignee: nobody → amckay
Waiting on r?s around: https://github.com/rtilder/signing-service/pull/1
r+ and merged.  What needs to be done in marketplace-env?
Signing server is there as per:

https://github.com/mozilla/marketplace-env/pull/76

What we need to figure out is how zamboni and signing service communicate. Whats the API, what auth it uses and what secrets the out of the box zamboni and signing service share.
Is there some docs on what needs to be shared and setup between zamboni and the signing-server, or do you want to do that?
Flags: needinfo?(rtilder)
With: https://github.com/rtilder/signing-service/pull/5 and https://github.com/mozilla/zamboni/pull/3015 we are close to working, we just get the error mentioned. Chatting rtilder in IRC it sounds like we need set up a new cert on Docker startup?
Assignee: amckay → rtilder
Closed as fixed based on the PR in #c6 being merged.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(rtilder)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.