-
Task
-
Resolution: Unresolved
-
Major
-
None
-
1.15.0.Final
-
None
-
False
-
False
-
We have two Quarkus extensions/addons that start kogito images.
These images are produced by kogito-images based on modules in kogito-apps.
Here's the data-index example; a similar one exists for tracing-addon:
The processes extension also upon the publication of a kogito image to quay.io; that is not built until kogito-apps and not published to quay.io until kogito-images.
This, in essence, means the kogito Quarkus extensions rely upon the last published quay.io image and hence are effectively "one version behind".
Is there anything we can do about this!?
- is related to
-
KOGITO-6684 Kogito images for supporting services should no longer download the runner jar from maven repository
-
- Closed
-
- relates to
-
KOGITO-5508 Add data index inmemory dev service to Kogito process extension
-
- Resolved
-
-
FAI-602 Integrate the AuditUI with the Quarkus DevUI
-
- Done
-