Skip to content

Sentry provider missing in v2, and v1 hardcoded sentry.io #1001

Description

@artile

v1 shipped a Sentry provider (Project, Team, ClientKey) under alchemy/sentry. v2 has no Sentry provider — packages/alchemy/src has no Sentry directory, and distilled/packages has no sentry SDK.

The v1 client also hardcoded the API host, so a self-hosted Sentry could never be managed:

// alchemy@0.93.12 — lib/sentry/api.js
this.baseUrl = "https://sentry.io/api/0";

Self-hosted Sentry exposes the same /api/0 surface, so the only blocker is that one constant. Axiom already models the shape this needs — Credentials carries apiBaseUrl with a DEFAULT_API_BASE_URL fallback.

I would like to port Sentry to v2 with a configurable API base URL from the start, and I am happy to write it. Three questions before I do:

  1. Do you want a Sentry provider in-repo, or was dropping it deliberate?
  2. Does it need a @distilled.cloud/sentry SDK first? Sentry publishes an OpenAPI schema, so generation looks feasible, but I don't know whether a small provider is allowed to use HttpClient directly.
  3. Is Project, Team and ClientKey the right scope to start with?

On testing: live tests need a Sentry org and an auth token with org:read, project:read, project:write and project:admin. The self-hosted path can be covered against a local instance, though that is harder to wire into CI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions