Skip to content

fix(backup): Preserve multiple project keys on import - #124253

Draft
sentry-junior[bot] wants to merge 1 commit into
masterfrom
fix/projectkey-relocation-import
Draft

fix(backup): Preserve multiple project keys on import#124253
sentry-junior[bot] wants to merge 1 commit into
masterfrom
fix/projectkey-relocation-import

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Sep 13, 2026

Copy link
Copy Markdown
Contributor

A project import triggers the normal provisioning signal, which creates a default ProjectKey. The ProjectKey importer then repeatedly reuses that row by project, silently overwriting earlier imported keys.

Suppress default-key provisioning while importing projects and insert each exported key independently. This preserves every DSN while retaining collision regeneration for imports into installations that already contain the key.

Fixes getsentry/self-hosted#4502

via Reinaldy Rafli.

--

View Junior Session [Sentry]

Co-Authored-By: Reinaldy Rafli <work@reinaldyrafli.com>
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Sep 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sentry import global silently drops all but one ProjectKey per project

0 participants