Skip to content

CSHARP-4953: dot-net-driver Evergreen Configuration May Be Leaking Secrets #1279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 4, 2024

Conversation

sanych-sun
Copy link
Member

No description provided.

@sanych-sun sanych-sun requested a review from a team as a code owner March 1, 2024 23:20
@sanych-sun sanych-sun requested review from rstam, JamesKovacs and BorisDog and removed request for a team and rstam March 1, 2024 23:20
@@ -1916,6 +1942,7 @@ task_groups:
params:
file: testazurekms-expansions.yml
teardown_group:
- func: upload-test-results
Copy link
Member Author

Choose a reason for hiding this comment

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

This change unrelated to leaking secrets, but it fixes missed tests results for some build variants.

Copy link
Contributor

@BorisDog BorisDog left a comment

Choose a reason for hiding this comment

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

Double check also
GCPKMS_SERVICEACCOUNT and ATLAS_SEARCH

Copy link
Contributor

@BorisDog BorisDog left a comment

Choose a reason for hiding this comment

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

LGTM.
Do we need also the check the nested scripts as well?

Copy link
Contributor

@JamesKovacs JamesKovacs left a comment

Choose a reason for hiding this comment

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

LGTM

I considered suggesting YAML anchors/aliases to remove the duplication in env var names, but it adds complexity.

You could add a `variables section at the top:

variables:
- fle_env_vars: &fle_env_vars
  - "FLE_AWS_ACCESS_KEY_ID"
  - "FLE_AWS_SECRET_ACCESS_KEY"
  - "FLE_AZURE_TENANT_ID"
  - "FLE_AZURE_CLIENT_ID"
  - "FLE_AZURE_CLIENT_SECRET"
  - "FLE_GCP_EMAIL"
  - "FLE_GCP_PRIVATE_KEY"

- other_env_vars: &other_env_vars
  - "A"
  - "B"
  - "C"

And then use it later:

include_expansions_in_env: *fle_env_vars

I'm OK with keeping the repetition and simplicity of the current impl.

@sanych-sun sanych-sun force-pushed the evergreen-experiments branch from 601e35b to a870e76 Compare March 4, 2024 23:40
@sanych-sun sanych-sun merged commit b77f339 into master Mar 4, 2024
@sanych-sun sanych-sun deleted the evergreen-experiments branch March 4, 2024 23:44
@sanych-sun sanych-sun restored the evergreen-experiments branch March 4, 2024 23:44
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.

3 participants