Allow passing a custom image size

[marinofelipe]

Context

The default image size is 90GB, which is often not enough to run the usual heavy Xcode-related workflows.

So, to avoid an image running out of space quickly, or an almost-full storage leading to decreased performance, users have to resize it afterward.

Something on these lines

• Use this amazing packer plugin to generate a new golden image
• Resize the image by running, for example
  • `orka3 vm deploy temp-resize --image $goldenImage
  • orka3 vm resize temp-resize 400
  • `orka3 vm save temp-resize $goldenImage2 --description $goldenImageCopiedDescription
  • orka3 delete temp-resize
  • .. and maybe even, before, delete the golden image and then save it with the same name

Idea

Given that this Packer plugin leverages the orka cluster and temporarily deploys a builder VM, it would be amazing if there was an optional configuration variable that defines a custom VM size.

image_size (int) (optional): A custom image size. By default, the image has 90GB.

source "macstadium-orka" "image" {
   # other vars ...
   image_name  = "golden-image"
   image_size  = 400

That could simplify the life for those using this plugin, and make the resizing approach more consistent.

There could be limitations and challenges, but nevertheless here's the idea :). I'd be happy to contribute and give it a try.

[celanthe]

Hi @marinofelipe! This is a wonderful suggestion that would bring a much needed improvement to the Orka Packer Plugin. I would love to work with you to help get this to fruition. :) If that's something you feel up to contributing, I'm happy to take a look at the PR when it comes in and test it myself in addition to our developer team's reviewers. I'm happy to pair with you as needed to get this shored up and validated so we can open a PR when it's complete. If that works for you, I'll assign the issue to you! :) Looking forward to connecting, and thank you again!