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.

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

Trigger harvesting on a schedule #4

Open
jvanulde opened this issue Jan 20, 2020 · 4 comments
Open

Trigger harvesting on a schedule #4

jvanulde opened this issue Jan 20, 2020 · 4 comments
Milestone
Sprint 2

Comments

@jvanulde
Copy link
Collaborator

jvanulde commented Jan 20, 2020 •
edited
Loading

Ideally, we will check for updates. In the mean time we can schedule them via chron.
@denevers
Copy link
Owner

One way to program chron in a container is described here

https://stackoverflow.com/a/47960145

@jvanulde
Copy link
Collaborator Author

Another way to handle this is to use the scheduling in Lamba.

@jvanulde jvanulde added this to the February 28, 2020 milestone Feb 20, 2020
@jvanulde
Copy link
Collaborator Author

Lets look at CloudWatch

@jvanulde jvanulde modified the milestones: February 28, 2020, Sprint 1 Apr 7, 2020
@jvanulde jvanulde modified the milestones: Sprint 1, Sprint 2 May 5, 2020
@jvanulde
Copy link
Collaborator Author

jvanulde commented May 5, 2020

In progress. Trigger exists we just need to decide when it gets called.

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
Sprint 2
Development

No branches or pull requests
2 participants
@jvanulde @denevers