database migration using argocd PreSync hook

[NissesSenap]

Hi

I'm currently thinking of is it possible to use Kargo with DB migrations.

Current way of working

When our applications need to perform a DB migration, we use a ArgoCD preSync hook that triggers a job.
The application and the DB migration solution are located in two separate containers.
We only trigger a build of the DB migration image when we update the schema.

So we only want the DB migration image to update when there is a new version, else it should keep the old one.
But when we need to run a DB migration, we want the container images to be updated in the same PR/workflow.

Question

I assume this isn't possible. But is there any way for me to trigger a stage that got two separate warehouses and update the image at the same time in two locations? But only when both of them has been updated. Else, I only want to update the application image.

I guess you can have 2 stages.

1. that updates the application container image and it only listens for the application container repo.
2. Listens for changes for the DB migration job, and updates both the application and DB migration image yaml.

But it will get a bit painful to maintain.
Anyone else have so good ideas how this can be solved?
Or do you think I should just solve this in argocd workflow in some nice way?