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

Better container propagated environment variables management #4

Open
tcojean opened this issue Oct 30, 2021 · 0 comments
Open

Better container propagated environment variables management #4

tcojean opened this issue Oct 30, 2021 · 0 comments

Comments

@tcojean
Copy link
Member

tcojean commented Oct 30, 2021

Currently, the environment variables which are passed to the container are managed through the hard-coded list PROPAGATED_ENV_VARIABLES in include.sh. This contains many Ginkgo-specific variables and needs to be configurable for generic use. It's not clear yet how the configuration can be best implemented. A simple way would be a configuration file the user needs to fill in the repository.

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

No branches or pull requests

1 participant