This plugin will require importing the mockbuild module.
Moreover I have not yet written tests.

Some comments and important notes are in the related Issue: #255

@mkoncek could you update the PR description including some information regarding this new plugin?, the purpose of the PR is clear but it'd nice having more background e.g. of use cases, invocation..

@mkoncek moreover, is there a plan to include documentation along with this new plugin? I cannot find anything other than _run_ansible docstring

@mkoncek moreover, is there a plan to include documentation along with this new plugin? I cannot find anything other than _run_ansible docstring

Right, of course, it would take some time though. I usually write more detailed documentation after having some prototype, but I don't expect many further changes.

One followup note: I miss the goodies we have in Command.run() - friendly command, logging, duration, exit code logging, stdout/stderr, timing events. I don't think it's a blocker, but I strongly believe the "run command on a guest" situation in log file should be plugin-agnostic - extra messages don't hurt as much as missing ones, makes the investigation of issues ridden with exceptions based on which provision plugin was used. It should be fixed ASAP.

1. I would start mirroring the functionality found in Command.run. There are a few questions related to dry run for example. Whether we should actually enter mock and run echo $command or just print the cmd.
2. I agree that the logging as written by me was quite ad-hoc and more for development. It does need to be unified with the rest of the sources.
3. I noticed that I had to write:

stdout = MockShell.Stream(lambda text: output_logger("out", text, 'yellow', level = 0))
stderr = MockShell.Stream(lambda text: output_logger("err", text, 'yellow', level = 0))

to get any output, I know that for example the container provision uses level=2, but I could not see the logs even when running tmt -vvv.

As i mentioned elsewhere, for this plugin to work, it needs to install a mock plugin into the mockbuild directory. Where should such file be placed in the source base of this project?

As i mentioned elsewhere, for this plugin to work, it needs to install a mock plugin into the mockbuild directory. Where should such file be placed in the source base of this project?

We don't have one, but you could make one like contrib or third_party and others will comment if they have a specific preference.

1. I would start mirroring the functionality found in Command.run. There are a few questions related to dry run for example. Whether we should actually enter mock and run echo $command or just print the cmd.
2. I agree that the logging as written by me was quite ad-hoc and more for development. It does need to be unified with the rest of the sources.
3. I noticed that I had to write:

stdout = MockShell.Stream(lambda text: output_logger("out", text, 'yellow', level = 0))
stderr = MockShell.Stream(lambda text: output_logger("err", text, 'yellow', level = 0))

to get any output, I know that for example the container provision uses level=2, but I could not see the logs even when running tmt -vvv.

It would help collecting these improvements in an issue.