After sentry project create or sentry init, the resolved project and DSN data isn't saved to the local DB. The next command (e.g. sentry issue list) has to re-scan files for the DSN and hit the API to resolve the project — even though all that info was just known.
Should seed project_cache and dsn_cache the same way resolveFromDsn and detectDsn do on their slow paths, so subsequent commands get cache hits.
Key places where the data is available:
createProjectWithDsn in src/lib/api/projects.ts — has orgSlug, project (id/slug/name), DSNcreateSentryProject in src/lib/init/local-ops.ts — has directory context for dsn_cache keying
After
sentry project createorsentry init, the resolved project and DSN data isn't saved to the local DB. The next command (e.g.sentry issue list) has to re-scan files for the DSN and hit the API to resolve the project — even though all that info was just known.Should seed
project_cacheanddsn_cachethe same wayresolveFromDsnanddetectDsndo on their slow paths, so subsequent commands get cache hits.Key places where the data is available:
createProjectWithDsninsrc/lib/api/projects.ts— has orgSlug, project (id/slug/name), DSNcreateSentryProjectinsrc/lib/init/local-ops.ts— has directory context for dsn_cache keying