feat: Add boil tool

[Techassi]

Caution

Once this merges, bake will no longer be compatible with this repository. As such, the GHA workflow needs to be adjusted to work with boil.

Note

This was ✨ magically ✨ developed in my spare time and I'm happy to fully hand over this code to Stackable.

This PR adds boil, a replacement for bake written in Rust.

• Adds more type-safety. The bake --preflight command is for example currently broken on main (even if unused).
• Adds more verbose and detailed error messages
• Separates local image dependencies from other build arguments
• Uses TOML for configuration files instead of Python modules
• Automatically appends _VERSION to local image versions ARGs
• Increases speed of data generation (before handing off to docker)
• Provide commands for structured output of various pieces of data

I additionally have some cool ideas (dealing with supported product versions for example), but I don't wanna spoil them just yet.

[NickLarsenNZ]

Worth pointing out that when this merges, bake will no longer work.

[Techassi]

Worth pointing out that when this merges, bake will no longer work.

Oh yeah, good point. I will add it to the description.

[xeniape]

Tried running cargo boil build airflow. Got this as a result:

WARNING: No output specified for entry--airflow-2_10_4, entry--airflow-2_10_5, entry--airflow-2_9_3, entry--airflow-3_0_1 target(s) with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Successfully built 4 images:
oci.stackable.tech/sdp/airflow:2.10.4-stackable0.0.0-dev-amd64
oci.stackable.tech/sdp/airflow:2.10.5-stackable0.0.0-dev-amd64
oci.stackable.tech/sdp/airflow:2.9.3-stackable0.0.0-dev-amd64
oci.stackable.tech/sdp/airflow:3.0.1-stackable0.0.0-dev-amd64

Images weren't there and running cargo boil build airflow --load or cargo boil build airflow -- --load didn't work.

[Techassi]

Images weren't there and running cargo boil build airflow --load or cargo boil build airflow -- --load didn't work.

The first of these two commands now works. In 65bab9c I've added the --load flag. This flag is only needed if using a driver/builder which does not load the final image into the local image store.

[xeniape]

Tested the commands from the README

• cargo boil build airflow --load
• cargo boil build airflow=3.0.1 --load
• cargo boil build airflow=3.0.1,2.10.5 --load
• cargo boil build airflow opa --load
• cargo boil show images

They worked for me now, thanks for adding the --load flag :)

Just some minor things I noticed while trying them out (don't need to be addressed if they have no consequences, just noting them down):

• Airflow build is showing warnings: => WARN: InvalidDefaultArgInFrom: Default value for ARG oci.stackable.tech/sdp/git-sync/git-sync:${GIT_SYNC_VERSION} results in empty or invalid base image name (line 10)
• The images being built all have the -amd suffix, which makes it a bit more annoying if I want to work with it locally since I have to possibly re-tag it

[Techassi]

Airflow build is showing warnings: => WARN: InvalidDefaultArgInFrom: Default value for ARG oci.stackable.tech/sdp/git-sync/git-sync:${GIT_SYNC_VERSION} results in empty or invalid base image name (line 10)

This is a warning emitted from Docker and should not be connected with any of the changes in tooling.

The images being built all have the -amd suffix, which makes it a bit more annoying if I want to work with it locally since I have to possibly re-tag it

They are now correctly tagged, because previously the images were tagged without the architecture, indicating it is a multi-arch image, even tho it was only ever one architecture (the one you specify, or linux/amd64 by default).

But let me know what we can maybe do to improve working with these images locally. One idea might be to tag them with and without the architecture suffix if a --local (name up for debate) flag is passed.