Closed Bug 1391032 Opened 9 years ago Closed 8 years ago

generate -stage environment configuration for new ops infrastructure

Categories

(Socorro :: Infra, task)

Product:
Socorro
Component:
Infra
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

Details

We have a docker-based environment and we have a socorro/config/docker_common.env file which contains all the environment configuration for running Socorro components in containers with docker-compose. That covers local development and running tests in CI. This bug covers taking that file and figuring out the values for Socorro -stage server environment and then getting that to Miles so he can use it for the new ops -stage server environment.
I think I'll just write a script that takes docker_common.env and the output of envconsul in -stage and fills in the appropriate values. I'm going to wait a bit to do this because configuration files get stale.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Summary: generate -stage environment configuration → generate -stage environment configuration for new ops infrastructure
Miles: We can work through this at the work week next week. Does that sound ok or do you need it sooner?
Flags: needinfo?(miles)
That sounds great!
Flags: needinfo?(miles)
We talked about this in person, and the gist was: :miles has based his configuration on the local dev env SHA f44d09d7385a756459d4d8e1e7ed768b1109d754. :willkg reviewed the configuration and found it sane. Whenever changes are made to the local dev env or if a separate file ala "use this env as a baseline for production" is created, we will figure things out in meatspace.
Given that, I think we're good here. Marking as FIXED. Thank you!
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.