Skip to content
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

Don't require secrets in medium e2e test #533

Closed
wants to merge 1 commit into from

Conversation

bbrowning
Copy link
Contributor

This removes the need to have any secrets in the medium e2e test itself, simplifying the setup across repos as multiple repositories run this job and it's tedious to have to sync those secrets in multiple places.

Note that the workflow itself still uses secrets to spin up the EC2 runners, but the actual e2e test job no longer uses any secrets.

This removes the need to have any secrets in the medium e2e test
itself, simplifying the setup across repos as multiple repositories run
this job and it's tedious to have to sync those secrets in multiple
places.

Note that the workflow itself still uses secrets to spin up the EC2
runners, but the actual e2e test job no longer uses any secrets.

Signed-off-by: Ben Browning <[email protected]>
@mergify mergify bot added the CI/CD Affects CI/CD configuration label Feb 1, 2025
@bbrowning
Copy link
Contributor Author

Oops! Duplicate of #530

@bbrowning bbrowning closed this Feb 1, 2025
@mergify mergify bot added the ci-failure label Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD Affects CI/CD configuration ci-failure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant