chore: db migration for integration events

[nunogois]

https://linear.app/unleash/issue/2-2435/create-migration-for-a-new-integration-events-table

Adds a DB migration that creates the integration_events table:

• id: Auto-incrementing primary key;
• integration_id: The id of the respective integration (i.e. integration configuration);
• created_at: Date of insertion;
• state: Integration event state, as text. Can be anything we'd like, but I'm thinking this will be something like:
  • Success ✅
  • Failed ❌
  • SuccessWithErrors ⚠️
• state_details: Expands on the previous column with more details, as text. Examples:
  • OK. Status code: 200
  • Status code: 429 - Rate limit reached
  • No access token provided
• event: The whole event object, stored as a JSON blob;
• details: JSON blob with details about the integration execution. Will depend on the integration itself, but for example:
  • Webhook: Request body
  • Slack App: Message text and an array with all the channels we're posting to

I think this gives us enough flexibility to cover all present and (possibly) future integrations, but I'd like to hear your thoughts.

I'm also really torn on what to call this table:

• integration_events: Consistent with the feature name. Addons are now called integrations, so this would be consistent with the new thing;
• addon_events: Consistent with the existing addons table.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
unleash-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 17, 2024 8:47am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
unleash-monorepo-frontend	⬜️ Ignored (Inspect)	Visit Preview		Jul 17, 2024 8:47am

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Manifest Files

[chriswk]

BIGSERIAL? we might be expecting more than 2B events here. Probably not, but moving to 8 bytes instead of 4 bytes here to never have to worry about it. Still going to give you a thumbsup, just something to consider.

[nunogois]

Thanks, addressed in ed64b1f

[chriswk]

Consider maybe using BIGSERIAL, but not a deal breaker for me. The rest of the table seems 👍