Running Webhooks Post Deployment Deletion

[sghegoiu-rokos]

Hi guys,

Im trying to setup an automation to call one of my webhooks when a deployment is deleted (I keep track of some other business specific metadata in another database which in turn need to be cleaned up when a deployment is deleted). I could potentially move my tables into the prefect db and cascade, but I'd prefer to avoid that if possible.

I have looked at Prefect automations and there is no way of triggering a webhook when a deployment is deleted.

Are there any other solutions you would recommend?

Thanks,
Stefan

[bdalpe]

Hi @sghegoiu-rokos,

We provide a prefect.deployment.deleted audit event in Prefect Cloud.

Don't see why we can't emit an event in OSS when this happens.

[sghegoiu-rokos]

That would work really well!

[sghegoiu-rokos]

sorry @bdalpe I had a follow up - I think I may be using the wrong entity here.

to give you a bit more context, Im working on exposing a generic workflow to our users to allow different AI prompts being run on a schedule. Initially I thought the right way to do this would be by creating a deployment per user-specific-schedule. However I noticed that the actual DeploymentSchedule entity would be much more appropriate for this.

However, DeploymentSchedule doesn't seem to have any event watching/emitting integrated at all.

What's your opinion on the most appropriate type to use for this kind of usecase? thanks!

[zzstoatzz]

@sghegoiu-rokos changing the schedule on a deployment would still trigger a deployment.updated event

you could match on the exact nature of that updated event in your automation's trigger definition

[sghegoiu-rokos]

ah that's great, thanks a lot!

in terms of scaling, is there any threshold of schedules past which you would recommend splitting the deployment up or can I add as many schedules as possible to the same deployment?

[zzstoatzz]

there aren't hard rules in open source as far as I'm aware. depending on how flexible your deployment parameters are, you might reasonably have 5-10 schedules for a deployment. it might become unwieldy beyond that, but that seems like its purely about your ergonomics

[sghegoiu-rokos]

thanks for that, good to know. I'll see what i come up with, im looking at maybe hundreds of schedules being created for the same deployment 😮‍💨