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
add dep sync in addition to fetch #88
Labels
Comments
groob
added a commit
to groob/micromdm
that referenced
this issue
Mar 22, 2017
For micromdm#88 load/save DEP cursor boltdb storage. Call sync once cursor is exhausted. The sync response handling is still a TODO.
groob
added a commit
to groob/micromdm
that referenced
this issue
Mar 22, 2017
For micromdm#88 load/save DEP cursor boltdb storage. Call sync once cursor is exhausted. The sync response handling is still a TODO.
groob
added a commit
to groob/micromdm
that referenced
this issue
Mar 22, 2017
For micromdm#88 load/save DEP cursor boltdb storage. Call sync once cursor is exhausted. The sync response handling is still a TODO.
groob
added a commit
that referenced
this issue
Mar 23, 2017
For #88 load/save DEP cursor boltdb storage. Call sync once cursor is exhausted. The sync response handling is still a TODO.
Done in #109 although not nearly complete(sync ops still need to be processed by device db). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The binary starts up and starts fetching devices from DEP.
We should rely on
sync
after the initial fetch is done, but for that to happen, we need to persist the cursor and other configuration so we in the same place where we left off after a restart.First solve: #87 which will require adding a dep configuration bucket.
The text was updated successfully, but these errors were encountered: