This will make it easy to pass the redis service URL into new containers.
Celery already comes with a config_from_envvar function, which is called explicitly for each variable we want to allow to be overridden from the environment, but ORES reuses this configuration itself, so we should probably pull the data out of the Celery app object after configuring it.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • ACraze | T195073 Use docker for ORES travis-ci tests | |||
| Declined | None | T195074 Make Celery `result_backend` and `broker_url` configurable by environment variable |
This is not needed as we have docker tests coming from a dedicated yaml file. Right? Reopen if that's not the case.
The details are vague to me at this point, but I think the issue was that we would be spinning up several docker containers and they have to be able to find each other. If we're getting the URLs configured some other way, that's fine!