Utilize odkrunner

[joeflack4]

Overview

We should utilize ODK runner instead of run.sh.

Additional info

• context
• Related: Document SOP for updating the repo sh run.sh make update_repo #435

[twhetzel]

@joeflack4 do you want to try this for updating to ODK 1.5.4?

[joeflack4]

I'm not in a rush to do this. I did notice when updating my images locally that there was a new image, but unless there's a specific benefit to a patch version, I feel it's better to wait.

Unless you or Nico know of a specific reason that we should upgrade to this version.

Similar with this one. This is a nice-to-have. So I'm not in a rush though I could do it after completing my January release issues.

I could do these in the same PR or separate; either way.

[matentzn]

I don't think there is anything "to do" to switch to ODK runner other than adding something to the documentation? We could possibly add a goal to upgrade ODK runner to the makefile but setting it up is a local job.

[joeflack4]

Good point. Well, looks like it's only a couple hundred kb (that makes me happy); in that case personally I'd commit that. But if we do, I agree; would still update the docs about using it.

But I guess the standard practice for a binary like this is manual setup, adding to global packages, if we just wanna go that route.

[joeflack4]

As for ODK version, I suppose @matentzn doesn't see a reason to upgrade right now either? Or on the contrary, I wonder if you guys do want to upgrade the mondo-ingest config on every minor/patch update, rather than case by case?

[matentzn]

I think it makes sense to update versions frequently as the minor versions are all about upgrading sssom, oak, robot etc.. So I would be in favour of upgrading. Minor updates don't happen more than once every two or three months, the last two were a real exception