Inform the user in log of environmental variables are being overwritten from image.
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
I have a pipeline that runs headless testing. Currently it's looking at CHROME_BIN, but there are lots of environmental variables that would be susceptible to this too. I bake this environmental variable into my image using buildah config this way it runs in the pipeline, and in executions outside for debugging.
I observed a case where an execution in the pipeline was different from my local execution in the container. This was reported to me in a ticket.
The reason for this was because the user of a fork of the repo had configured the CI Environment to override CHROME_BIN. IT would be nice if the raw-log notified me of that..
OVERRIDING IMAGE ENVIRONMENTAL VARIABLE $VAR WITH GITLAB-CI CONFIGURATIONFor this GitLab could inspect the image with podman inspect or the like, and warn the user if the GitLab CI's UI-inputs conflict with the image.