Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement "backfilling" capability #22

Open
markborkum opened this issue Jan 25, 2019 · 2 comments
Open

Implement "backfilling" capability #22

markborkum opened this issue Jan 25, 2019 · 2 comments

Comments

@markborkum
Copy link
Contributor

Pacifica Notifications version

n/a

Pacifica Core Software versions

n/a

Platform Details

n/a

Scenario:

Currently, clients of pacifica-notifications may create, read, update and delete event subscriptions. The side-effect of creating a new subscription is that the client receives CloudEvents notifications for future Pacifica transactions only.

This feature request is for "backfilling", whereby the client requests CloudEvents notifications for past Pacifica transactions.

Steps to Reproduce:

The client issues an HTTP request to a new pacifica-notifications endpoint, where the payload of the HTTP request is that of the "create" endpoint, but also includes additional two timestamps that collectively specify a time interval.

Expected Result:

The client receives CloudEvents notifications for Pacifica transactions that occurred in the past within the specified time interval that match the specified criteria (i.e., the JSONPath).

Actual Result:

n/a

@dmlb2000
Copy link
Member

This will need a corresponding ticket in the pacifica-metadata and pacifica-policy packages to provide an endpoint to query.

The trick with this feature is that we should allow the user to query for some number of past events but, only ones they are allowed to replay. We do have some context that can limit the query depending on where we allow this feature.

An unrestricted replay mechanism should only be allowed for administrators (and should probably be a second ticket in pacifica-metadata).

@dmlb2000
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants