We currently package the service changelog with the image in order to be able to read them in the cloud.
Theoretically, the image itself, from a functionality standpoint, can be reused.
It's just the changelogs themselves that vary.
So basically we create new docker images every time simply because we want to package the newest version of the changelog.
SIstead of using docker as a glorified data archive, we could reuse the liquibase and flyway images,
upload the service changelogs to a storage bucket and read the contents from there.
We currently package the service changelog with the image in order to be able to read them in the cloud. Theoretically, the image itself, from a functionality standpoint, can be reused. It's just the changelogs themselves that vary. So basically we create new docker images every time simply because we want to package the newest version of the changelog. SIstead of using docker as a glorified data archive, we could reuse the liquibase and flyway images, upload the service changelogs to a storage bucket and read the contents from there.