Skip to content

[e2e] Allow e2e tests to declare custom env variables - #69441

Open
emargetis wants to merge 1 commit into
erikmargetis/resource-setup-flagfrom
erikmargetis/e2e-per-test-env
Open

[e2e] Allow e2e tests to declare custom env variables#69441
emargetis wants to merge 1 commit into
erikmargetis/resource-setup-flagfrom
erikmargetis/e2e-per-test-env

Conversation

@emargetis

@emargetis emargetis commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

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_Hostport which change the behavior of Teleport. This builds on top of the work for config in #68769

Context

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
Chain: Cloud Panel E2E Testing
└── teleport: Add no-resource-setup flag to e2e runner 
    └── e: Add cloud panel e2e test
        └── teleport: Allow e2e tests to declare custom env variables ← current branch
            └── e: Enable Cloud Panel Test in CI

* Note that depending on timing, I may add the last two CI PRs directly to the new monorepo instead.

Manual Test Plan

Test Environment

Local

Test Cases

@emargetis emargetis changed the title initial draft [e2e] Allow e2e tests to declare custom env variables Aug 6, 2026
@emargetis
emargetis marked this pull request as ready for review August 6, 2026 22:34
@emargetis emargetis added no-changelog Indicates that a PR does not require a changelog entry backport/branch/v18 labels Aug 6, 2026
@github-actions
github-actions Bot requested review from bl-nero and ryanclark August 6, 2026 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/branch/v18 no-changelog Indicates that a PR does not require a changelog entry size/md

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant