On Sun, May 11, 2025 at 8:54 PM Michael Peddie michael.peddie@gallagher.com wrote:
Hi Milosz,
I am defining the variable in the env.yaml found in /etc/lava-server on the lava server host (which is separate from the worker host). I don't believe I am mistaken in that workers can use the variables defined there? I have been using it for some time (in particular for repository-based tests) and thought it might still be possible to use it in an interactive test.
you're right. I didn't understand it from your initial email.
As mentioned originally, I did have some success doing this, but it appears inconsistent. I was wondering if I could somehow get it to work or if there was an alternative? I am trying to avoid using an overlay, for various reasons, but if it is totally necessary to use it then that isn't a major issue.
environment options are passed to lava-run: https://gitlab.com/lava/lava/-/blob/master/lava/dispatcher/lava-run?ref_type... They may not be used where you expect them.
The images..image...headers in deploy you show, does it allow the passing of a username and password instead? As well, one or both pieces of information in the form of a variable rather than raw/hardcoded into the job?
Yes, works for basic authentication as well. You need to encode it with base64 as described here: https://www.debugbear.com/basic-auth-header-generator
It assumes the webserver recognizes the Authorization header.
Best Regards, Milosz