Wiki source code of V1.0.0
Last modified by Carlijn Kokkeler on 2024/07/17 14:46
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}}((( | ||
| 3 | These are the release notes for this runtime image. Once a runtime image is released, every new release will utilize this runtime image as base for creating runtime images for docker. | ||
| 4 | |||
| 5 | ====Infrastructure updates==== | ||
| 6 | 1. Can support gen 2 and gen 3 runtimes | ||
| 7 | 2. Instances have the latest security updates | ||
| 8 | 3. Deployment is done through the deployment plan | ||
| 9 | 4. On premise runtime deployment through the eMagiz portal (after installing the control agent) eliminating the need to locally install runtimes | ||
| 10 | |||
| 11 | ====Runtime specific updates==== | ||
| 12 | 1. Faster startup time | ||
| 13 | 2. Latest spring libraries providing latest bug fixes and security updates | ||
| 14 | 3. Logging will no longer have the flow origin but will have the container from which the logging resides | ||
| 15 | 4. Gen 3 metrics will be available giving more insight into your application and a better user experience | ||
| 16 | 5. Gen 3 logging will work slightly different but have a similar user experience. The 'Logger' field in logging details is replacing the 'Flow' field from gen 2. Also the container field is added so you can see from which container the logging originated. The bundle field from gen 2 is no longer relevant anymore for gen 3. | ||
| 17 | 6. Properties of a runtime are updated by creating a new release and deploying the new release through the runtime dashboard | ||
| 18 | 7. Runtime dashboard is currently not supported | ||
| 19 | |||
| 20 | ====Runtime specific update for legacy runtimes (Karaf)==== | ||
| 21 | 1. Gen 2 runtimes on gen 3 infra will reset every time to the active release when woken up or restarted. Meaning they will run the flows in the active release only, flows not in the active release will be gone even if they were there before putting a cloud slot on standby. | ||
| 22 | |||
| 23 | |||
| 24 | )))((({{toc/}}))){{/container}} | ||
| 25 | {{/container}} |