-
|
Is there any advice for how one would move from an existing in-house webhook delivery implementation to Outpost? (taking into account existing in-flight webhooks, and historical data to show in the UI?) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
We have the migration guide planned. But I hadn't thought about the historical data question. Migrating the webhook subscriptions will require mapping your existing subscriptions to new subscriptions (Destination resources) in Outpost. A script that uses the Outpost API is the likely approach to that step. Webhook delivery from an existing system would likely need to be stopped during migration. However, I'll see if we can recommend a staged approach with minimal downtime. Sometimes it's a good practice to slowly migrate traffic to a new component, so I'll see if we can define a way of achieving that. At present, migrating historical data would require direct DB interaction. It would be a matter of extracting your existing data and mapping it to the Outpost format. At the least we can provide the schema. |
Beta Was this translation helpful? Give feedback.
-
|
Work in progress migration guide with a few outstanding questions: Some specific outstanding pages:
|
Beta Was this translation helpful? Give feedback.
-
|
The historical data is tricky indeed.
I agree with this. I don't see a better solution for now. Maybe we can provide an example script of some sort. The tricky thing is even after migrating the data, they still need to make sure the data is updated with the stream of events. We can potentially provide an example script of some sort but ultimately it still depends on the user's schema and preferred language. |
Beta Was this translation helpful? Give feedback.
-
|
We now have a migration guide https://outpost.hookdeck.com/docs/guides/migrate-to-outpost |
Beta Was this translation helpful? Give feedback.
We now have a migration guide https://outpost.hookdeck.com/docs/guides/migrate-to-outpost