Create congregate container without mongo install
Overview
In an effort to decouple additional components from the congregate container, we need to move towards using a standalone mongo container.
This is somewhat of a breaking change, so this issue covers creating an additional congregate image and not updating the current rolling and release images
A followup issue will need to be created to update the default value of the mongo host once we get closer to fully decoupling mongo from the main congregate image
Tasks
-
Create a new congregate Dockerfile under docker/release called no-mongo.Dockerfile
-
Use centos.Dockerfile
as the starting point for this new file -
(Optional) Try setting up the image with a UBI image as its base image. You should be able to use our existing centos.Dockerfile as a starting point if you go this route as well -
Remove all references to mongo in no-mongo.Dockerfile
-
Create a CI job building and pushing this image as "rolling-no-mongo:latest" -
Update docs if needed (workflow, runbooks, README, migration metrics, etc.)
Acceptance Criteria
-
A new image is pushed to the container registry -
Running mongo on the container should result in a "command not found" error -
100% code coverage on new code
@gitlab-org/professional-services-automation/tools/migration
Edited by Alex Rosencrans