Skip to content

epi_archive to pure S3 #235

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.

Sign up for GitHub

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

Jump to bottom
Closed
dsweber2 opened this issue Sep 12, 2023 · 2 comments
Closed

epi_archive to pure S3 #235

dsweber2 opened this issue Sep 12, 2023 · 2 comments

Comments

@dsweber2
Copy link
Contributor

Not sure if this exists as an issue or only in people's head, but it was an OKR that seems like its been hanging around. Seems like there was not useful overhead that arose from R6 that people wanted to ditch.
The specific summer OKR item was

Move epi_archive from R6+S3 to S3 only, encapsulate fields, add filter method
which seems like several issue to me
@dajmcdon
Copy link
Contributor

@dsweber2 This is an epiprocess issue not epipredict. Can you move there?

@dsweber2
Copy link
Contributor Author

Right, that does make more sense of why I couldn't find it. There's an outstanding issue there: cmu-delphi/epiprocess#340.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dsweber2 @dajmcdon