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

Support different sync policy for extra remotes #106

Open
bhou opened this issue Jan 1, 2023 · 0 comments · May be fixed by #146
Open

Support different sync policy for extra remotes #106

bhou opened this issue Jan 1, 2023 · 0 comments · May be fixed by #146

Comments

@bhou
Copy link
Collaborator

bhou commented Jan 1, 2023

In v.1.8.0, the command launcher starts to support multiple remotes. With more remotes defined, this will make the update process long at the end of command calls. We can solve this issue by introducing different sync policies for each remote:

  • never
  • always
  • hourly
  • daily
  • weekly
  • monthly
@bhou-crto bhou-crto linked a pull request Dec 31, 2024 that will close this issue
Open
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

Successfully merging a pull request may close this issue.

Support remote sync policy criteo/command-launcher
1 participant
@bhou