https://github.com/os-autoinst/openQA/pull/613
https://github.com/os-autoinst/os-autoinst/pull/452

The changes enabling this behaviour are in the upstream repos now:
• https://github.com/os-autoinst/openQA/pull/613
• https://github.com/os-autoinst/os-autoinst/pull/452

Do we have any idea how long it takes from that point to us having the code deployed?

If the changes are easily backportable I can have it deployed tomorrow morning, it's just a case of backporting the patches, kicking out new package builds and updating the servers. Do you want me to do that?

In D744#15179, @adamwill wrote:

...it's just a case of backporting the patches...

I can even provide patches for our current packages, as I've been developing it on top of that. Yeah, I could not find a sane way to run openqa/os-autoinst from git, so I've been in fact "forward-porting" the changes :D

Then by all means just sling the patches at me somehow or other and I'll bump the package.

I've had the updated openQA/os-autoinst running on stg all week and it seems fine, so I'm applying it to prod now. The update will go stable tomorrow.

I'm fine with this change in principle, it will probably need some rediffing now though.

This is going to be a PITA for creating new needles, because I think the web UI will always create them in the top level directory, and we'll have to move them manually before commit :(

In D744#16207, @adamwill wrote:

This is going to be a PITA for creating new needles, because I think the web UI will always create them in the top level directory, and we'll have to move them manually before commit :(

Yeah, that's unfortunate. OTOH, I find current structure to be much more readable.