What's the "correct way" to provide the test runner with some secrets/credentials? about unity-test-runner

[alexiscatnip]

@webbertakken 👍 thanks so much! I am presently not familiar with building docker (only know how to docker run).

I will investigate one of these days... For now I just quickly forked the repo and hard-coded my 3 values to pass in; something like -env MY_SECRET_FROM_GITHUB_SECRETS. It more or less works... :'')

[alexiscatnip]

Looking at
https://github.com/game-ci/unity-test-runner/blob/3d5d2f58348b293ae1fe6b7cca24deccaf505b2f/src/model/docker.ts ,
I think I can modify the command line string, by adding in my env variables (hard-code...).

But that might be thinking too much inside the box?

[alexiscatnip]

By using the shell of the github runner VM, I am able to read the envs.
https://github.com/alexiscatnip/github_action_experiment/tree/main

My present suspicion is 'the envs of the github VM are not inherited by the docker container, and instead must be defined in the CLI arguments as a flag like --env MYENVVAR"

[webbertakken]

You are correct in your observation that we're not passing non-specific env variables into the container.

You can use customParameters to pass any parameters into the image and read them from your code.

Here's an example of how to read the variables that you've passed from builder. Effectively the same can be done in your test setup.

Let me know if this sufficiently answers your question.