[e2e] Allow e2e tests to declare custom env variables - #69441
Open
emargetis wants to merge 1 commit into
Open
Conversation
2 tasks
emargetis
marked this pull request as ready for review
August 6, 2026 22:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds support for e2e tests to declare their own set of env variables.
This enables us to set env variables like
Teleport_Cloud_Hostportwhich change the behavior of Teleport. This builds on top of the work for config in #68769Context
Contributes to https://github.com/gravitational/cloud/issues/17873
This is the third PR in a chain to add an e2e test to the enterprise repo that asserts the Usage Reporting page can be fetched from the Cloud API and successfully loaded.
PR chain
Manual Test Plan
Test Environment
Local
Test Cases