Open kobalicek opened 1 year ago
The way it works right now is because I want to minimize the risk of an update of the action or an image would break existing usages of the action. If a new OS version of an image would require different flags when starting the hypervisor then that would break if the action is not updated as well.
Hmm, possibly if the image itself shipped with a list of flags for the hypervisor. Then there would need to be two sets of flags, one set for QEMU and one for Xhyve. There would also need to be someway to indicate which version is the latest, I guess that could just be a text file next to the images.
Yeah that would be amazing if the action can just pick it up.
BTW if it's something that you don't plan to work on I would just close the issue as WONTFIX, I just had this idea and it would help me maintaining my workflows.
I don't have anything against the feature per se. I think it's a reasonable enhancement request. But I don't plan to work on it now. I think there are more pressing things to work on, like the issue you have reported 😃.
I'm not sure this is easy or not, but I would welcome to just say "latest" when it comes to OS version.
The motivation is that I want to test BSDs, for example, but I'm just okay if my code builds & works on the latest version. This would save me from changing versions in workflow files, which means I would not have to track the support for new versions added to cross-platform-actions.