Skip to content

Better container propagated environment variables management #4

@tcojean

Description

@tcojean

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions