Steps to Reproduce:
1. Run a task that relies on env vars defined with Environment: in testinfo.desc (for example /distribution/beaker/dogfood)
Restraint should set the environment variables in the task's execution environment.
What are the chances of getting this feature implemented? In BaseOS CI, it was recently pointed out that its jobs - which use restraint to run the tests - ignored "AVC_ERROR=+no_avc_check" passed in rpm's testinfo.desc, and we found out it is indeed imperfection of restraint. As it's quite a common way of disabling AVC denials checks during runtime of the test, we'd appreciate the implementation of this feature.
If the same environment variable is defined in both the job XML and testinfo.desc, which has the higher priority?
It should be: a task parameter in the job XML overrides a testinfo.desc Environment setting.
You could dig through beah's implementation to verify that this is true for beah (we would want restraint to follow beah's behaviour in this regard).