This EPIC tracks the requirements for a builder image to get up to speed with Kogito Serverless Workflow applications in the cloud and on local environments without the need to install the prereqs to build a Java application.

The outcome of this EPIC is a builder image capable of receiving the resource files for a Kogito Workflow application and building a Quarkus application from it.

These resource files can be:

1. Descriptors for remote service invocations such as OpenAPI, gRPC, and Async files
2. Application properties
3. Workflow definition files (workflows, subflows, functions, events, and so on)
4. Java files that implement custom functions

This builder image must have the option to cache external libraries in a volume, so tools or users reuse the image amongst other build cycles within the environment. Therefore, this image can be two-flavored, whereas one huge image would include everything on it up front, and the other would rely on external storage.

The target of the builder image is not to be used as a parent image for the target application but rather to generate an image from it.

Users can replace this builder image in their environment if possible, so the image must have a clear and documented way of its requirements and interface. Perhaps a lightweight version to be used as a base image.