passing?

Author: baileympearson

.evergreen/config.in.yml

@@ -1417,14 +1417,12 @@ task_groups:
         params:
           working_dir: "src"
           binary: bash
+          env:
+            DRIVERS_TOOLS: ${DRIVERS_TOOLS}
           args:
             - .evergreen/setup-serverless.sh
-
       - command: expansions.update
         params:
-          # this adds information about the serverless instance
-          # that is used by the cleanup group.  alternatively, we could source `serverless.env`
-          # in the cleanup group
           file: src/serverless-expansion.yml
 
     teardown_group:

.evergreen/config.yml

@@ -4448,6 +4448,8 @@ task_groups:
         params:
           working_dir: src
           binary: bash
+          env:
+            DRIVERS_TOOLS: ${DRIVERS_TOOLS}
           args:
             - .evergreen/setup-serverless.sh
       - command: expansions.update

test/readme.md

@@ -297,7 +297,7 @@ When you run the benchmarks verify that the BSON version has been picked by the
 
 ## Secrets
 
-Secrets needed for testing in special environments are managed in a drivers-wide AWS secrets manager vault.  
+Secrets needed for testing in special environments are managed in a drivers-wide AWS secrets manager vault.
 
 drivers-evergreen-tools contains scripts that can fetch secrets from secrets manager for local use and use in CI in the [.evergreen/secrets_handling folder](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/secrets_handling/README.md).
 
@@ -311,7 +311,7 @@ Local use of secrets manager requires:
 Here's an example usage of the tooling in drivers-evergreen-tools that configures credentials for CSFLE:
 
 ```bash
-bash ${DRIVERS_TOOLS}/.evergreen/secrets_handling/setup-secrets.sh drivers/csfle 
+bash ${DRIVERS_TOOLS}/.evergreen/secrets_handling/setup-secrets.sh drivers/csfle
 source secrets-export.sh
 ```