ECR Image registry event-based refresh

[AlanLonguet]

I see a lot of webhook implementations coming in and I'm starting to prepare how I'll be able to integrate ECR with the generic webhook implementation you're providing or if I should do something completely different.

Since ECR has no HTTP webhooks out of the box, we have to setup an EventStore and an SQS in all cases to be able to receive push events, with that in mind I have 2 implementations that could fulfill this problematic :

• The first one involved deploying an AWS Lambda that listens to those events and forward a simple http call to Kargo generic webhook in order to trigger the refresh
• The second one involved deploying a workload alongside Kargo that also listens to those events but bypasses the webhook feature to directly annotate warehouses in order to refresh them

Which path do you think I should follow ? And if you have another path that involves less complexity I'm all ears !

[krancour]

... an AWS Lambda that listens to those events and forward a simple http call to Kargo generic webhook in order to trigger the refresh

The generic receiver won't land until v1.7.0, but what you've described in your first option is the exact kind of use we had in mind for that receiver.

Your other option seems it also would work nicely.

I don't really have a specific opinion on which of these two is better. (I've also not personally done the first option. I'm merely aware it's a thing that people do indeed do.)

The advantage I would cite for the second option is that you could make that work today and you'd not need to wait for the generic receiver to land in v1.7.0.

[arnaudmm]

I'm also interested by this topic, @AlanLonguet have you chosen and implemented a solution yet? Solution 1 looks good. What I'm affraid with Solution 2 is to skip some Kargo internal stuff that could happen (now or in the future) like notifications + the lack of logs on Kargo side

[krancour]

An API for user-defined receiver logic is for sure landing in v1.9.0. (It was twice deferred because it was harder than we'd originally guessed and we didn't want to get it wrong.) With the holidays approaching, I'm hesitant to make any promises, but I would be shocked if v1.9.0 didn't land before the end of the year.