Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
This PR removes the workaround added in #73.
The goal of #73 was to fix a seemingly random loss of
curl
being installed in the Docker container.I noticed that
libcurl3
was being installed as part of the "Setup Mongo" step. Some googling led me to learn thatlibcurl3
cannot be installed withlibcurl4
, which is used bycurl
. So it appears that installinglibcurl3
also causedcurl
to be uninstalled since it's missing a dependency.I followed Mongo's instructions to just install a newer version of the mongo shell. Docs here
QA steps
Risks
I'm not sure why we pinned the mongo version. But if we are using it to just run a few queries to set up the database, it seems safe to bump the version.
Note that we bumping from version
4.2
to5.0
. I'm unaware of any breaking changes here.Rollback steps