Skip to content

Conversation

baileympearson
Copy link
Contributor

@baileympearson baileympearson commented Jan 27, 2025

Description

What is changing?

Serverless tests use AWS secrets manager to fetch credentials to set up the cluster. These tests don't use secretes manager to fetch FLE credentials (https://jira.mongodb.org/browse/NODE-6685).

I also updated the testing readme with instructions on how to use secrets manager and how to setup serverless tests locally.

Is there new documentation needed for these changes?

No.

What is the motivation for this change?

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

  • Ran npm run check:lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

. ./set-temp-creds.sh
popd
MONGODB_URI="${MONGODB_URI}" \
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Defining these variables does nothing.

source $DRIVERS_TOOLS/.evergreen/init-node-and-npm-env.sh

if [ -z ${SERVERLESS+omitted} ]; then echo "SERVERLESS is unset" && exit 1; fi
if [ -z ${SERVERLESS_URI+omitted} ]; then echo "SERVERLESS_URI is unset" && exit 1; fi
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This variable is never used in our tests because we use the load balanced URIs instead.

serverApi?: ServerApi;
activeResources: number;
isSrv: boolean;
serverlessCredentials: { username: string | undefined; password: string | undefined };
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is never set nor used.

tests will be skipped.

Below is a summary of the types of test automation in this repo.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a markdown linter installed locally. I figured the whitespace changes were fine. I'm also happy to unformat the file or install a markdown plugin for eslint instead.

@baileympearson baileympearson marked this pull request as ready for review January 28, 2025 14:50
@baileympearson
Copy link
Contributor Author

closing in favor of #4385

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant