sentry-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fahd Siddiqui (JIRA)" <>
Subject [jira] [Commented] (SENTRY-2269) Make SentryStore pluggable
Date Wed, 13 Jun 2018 22:25:00 GMT


Fahd Siddiqui commented on SENTRY-2269:

[~akolb] cc. [~spena] - The use case is that one may want to have an implementation of SentryStore
to store the data in a shared environment or proxy the calls to a cloud service instead of
a database for persistence. I don't have a use case for other components, but they can. Can
you explain "stability levels of SentryStore interfaces"? If you mean pinning it down, then
this change doesn't make any claims about that. It only concerns itself by making it a pluggable
interface. SentryStoreInterface can be refactored later if it is deemed necessary.

I don't intend to include an alternative implementation to Sentry, since it will be a pluggable
implementation separate from Sentry code base. 

> Make SentryStore pluggable
> --------------------------
>                 Key: SENTRY-2269
>                 URL:
>             Project: Sentry
>          Issue Type: Improvement
>          Components: sentrystore
>    Affects Versions: 2.1.0
>            Reporter: Fahd Siddiqui
>            Assignee: Fahd Siddiqui
>            Priority: Major
>         Attachments: SENTRY-2269.1.patch
> Make SentryStore pluggable so a different implementation can be plugged in at run-time
using a config property ("sentry.service.sentrystore"), similar to what we have for processor
> This would entail extracting all public methods of SentryStore to a SentryStoreInterface
and converting all call sites to program to the interface. 
> It will default to the existing SentryStore.

This message was sent by Atlassian JIRA

View raw message