Summary

Remove the legacy script set-temp-creds.sh after drivers migrate to the preferred alternatives.

Motivation

The preferred alternative does not require drivers manually pass credentials. This may help reduce likelihood of exposing test credentials.

The legacy script is not expected to be updated to support testing DRIVERS-2924.

Who is the affected end user?

DBX devs.

How does this affect the end user?

Removing set-temp-creds.sh runs the risk of breaking existing driver tests. It may be easy to verify current driver dev branches are not using this script, but it may be harder to check all supported release branches. Consider posting in #dbx-encryption to check with downstream teams.

The Ruby driver uses set-temp-creds.sh .

The C driver r2.2 and r1.30 release branches this script. r1.30 support is planned to drop April 1st, 2026. r2.2 is expected to drop after the 2.3.0 release.

How likely is it that this problem or use case will occur?

N/A?

If the problem does occur, what are the consequences and how severe are they?

N/A?

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.

Acceptance Criteria

• Remove set-temp-creds.sh.