From 323eb6ca5bda1163870410a8ebe43115a80cab50 Mon Sep 17 00:00:00 2001
From: Nicholas McDonnell <50747025+mcdonnnj@users.noreply.github.com>
Date: Wed, 22 May 2024 20:59:18 -0400
Subject: [PATCH] Remove the custom Cargo configuration

In the move from Alpine Linux 3.17 to 3.18 we also moved from Cargo
1.64.0 to 1.71.1. This takes us past 1.68, which introduced sparse
registries, and 1.70, which made `sparse` the default protocol to use
with crates.io (the default registry). This resolves #38, and based on
testing it also resolves #32.
---
 Dockerfile      | 3 ---
 src/config.toml | 7 -------
 2 files changed, 10 deletions(-)
 delete mode 100644 src/config.toml

diff --git a/Dockerfile b/Dockerfile
index 7ccba10..4212456 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -44,9 +44,6 @@ RUN apk --no-cache add \
   python3-dev=3.12.7-r0 \
   python3=3.12.7-r0
 
-# Copy in our custom Cargo configuration file
-COPY src/config.toml /root/.cargo/
-
 # Install pipenv to manage installing the Python dependencies into a created
 # Python virtual environment. This is done separately from the virtual
 # environment so that pipenv and its dependencies are not installed in the
diff --git a/src/config.toml b/src/config.toml
deleted file mode 100644
index d46bea6..0000000
--- a/src/config.toml
+++ /dev/null
@@ -1,7 +0,0 @@
-[net]
-# Configure Cargo to use the git CLI instead of the libgit2 library. There is
-# an issue with 32-bit (non-x86) platforms when libgit2 tries to pull down the
-# Cargo package index from GitHub. This *might* get fixed in a later version
-# of Cargo so it is being tracked in:
-# https://github.com/cisagov/code-gov-update/issues/32
-git-fetch-with-cli = true