1361439 - Create dockerflow-compliant container that runs a BMO web head

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: General, enhancement)

Description

[Dylan Hardison [:dylan] (he/him)]

A first step towards running bugzilla-dev (and eventually, all of bugzilla) in cloud-services infrastructure will be supplying a container that runs the a BMO webhead. 

BMO may require exceptions or changes to the dockerflow requirements, but the best way of proceeding is to be able to stand something up.

Comment 1

[Dylan Hardison [:dylan] (he/him)]

I'm at the point where I need to know how secrets and other config data can be passed in.

All my configuration can come in the format of this file: https://github.com/mozilla-bteam/bmo/blob/master/vagrant_support/checksetup_answers.j2

but I need to know how the stuff built around the containers passes that to the container's entry point.

Cheers!

Comment 2

[Chris Kolosiwsky [:ckolos] (ckolos has left the building)]

:dylan

All container configuration is done via 1 of 2 ways:

1) As env vars
2) Via config files

In both cases, puppet does the heavy lifting. For ENV vars, those are dumped to a file, /etc/dockerflow/${env}.txt. This file is then referenced when the systemd unit is created and passed to the container. In the event that a configuration file is required/wanted, the file is created as a puppet template and put into place when last-mile configuration of the application is done.

We store secrets in a private repo. Access to those is limited to members of cloudops only.

Comment 3

[Dylan Hardison [:dylan] (he/him)]

Attachment: PR

Comment 4

[Dylan Hardison [:dylan] (he/him)]

Comment on attachment 8871580 [details] [review]
PR

this was approved in github