Working on os-autoinst/os-autoinst#1558 this
idea came back to mind. I had already thought about doing something
similar couple of times, also based on requests by other users to be
able to test os-autoinst changes more easily. With this change it
should be possible to execute an arbitrary command within the worker
based on a job setting. For example the use case I envision is to
build a container image from a still open pull request of os-autoinst
and execute tests on a production instance without harmful impact of
the general environment, e.g.
podman run --rm -it registry.opensuse.org/devel/openqa/....
This could also be helpful for customized backend environments needed
to access other, more exotic hardware and such.
- AC1: "isotovideo" is not hardcoded as only choice within the openQA worker engine
- Status changed from In Progress to Resolved
https://github.com/os-autoinst/openQA/pull/3804 is merged, deployed and effective in a way that given right permissions it works as designed. During the work on https://hackweek.suse.com/20/projects/automated-test-for-game-plus-only-web-based-dev-plus-python-openqa I tried it out on openqaworker7 and have adjusted apparmor a bit locally. However likely we need to tweak further so that the user
_openqa-worker can do more as well, e.g. execute podman. I will leave this for the parent epic though.