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

Propagate Environment Variables to VSCode Testing Frameworks #630

Open
alexwilson1 opened this issue May 3, 2024 · 0 comments
Open

Propagate Environment Variables to VSCode Testing Frameworks #630

alexwilson1 opened this issue May 3, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@alexwilson1
Copy link

alexwilson1 commented May 3, 2024

We have some Python integration tests that are only able to run when they have environment variables from the cluster available. When using B2K and running a Python app normally (e.g. debug) it works, however, the Python tests and the Pytest framework don't seem to have access to the cluster environment variables.

If I run a 'printenv' in the terminal (after bridging kubernetes) I also don't see any of the cluster environment variables available. Could be related?

Would appreciate any pointers on how to get this working. Thanks for the great extension!

Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:43:08.196Z (3 wks ago)
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
@alexwilson1 alexwilson1 added the enhancement New feature or request label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant