Acceptance tests: manual upgrades

[ldevulder]

Split of #28

Manual upgrades, following cOS default usage and ros-installer

[ldevulder]

Playing with Dockerfile and elemental cli to see how it works, as I mainly used it through Rancher.

[ldevulder]

@mudler for manual upgrade I think that executing something like elemental upgrade -d quay.io/costoolkit/os2:v0.1.0-amd64 is enough?

In a e2e test I think I can install the latest released version in a VM and upgrade it to the latest build one with this kind of command. Pretty much what is already done with the e2e test with Rancher, but manually :-)

[mudler]

in a e2e test scenario I think we could even push some releases here over github so we can pick them up somehow in the tests.
In c3os I played with this and ended up to pull off latest artifacts releases from github and giving them as input iso: https://github.com/c3os-io/c3os/blob/master/.github/workflows/image.yaml#L308 As test suites run over SSH, at the end is easy enough to hook em up from a different medium

[ldevulder]

https://github.com/c3os-io/c3os/blob/master/.github/workflows/image.yaml#L308

Interesting! I also upload/download for the current build but a handmade code to download the lastet build, sounds easier with robinraju/release-downloader. I will give it a try then!