You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use case
Running the container as a script, just execute a single cycle
Describe the solution you'd like
While the container could be up and running and set with whatever poll frequency desired, for my use-case the polling is infrequent and upon request really. I'd like to be able to run the container with a single sync cycle instead of polling. Maybe if it's set to 0 or something?
Describe alternatives you've considered
I could start the container upon request, and have it automatically stopped after a set amount of time that ensures a sync completes but no second sync is started. While it would work, it's not exactly an elegant solution.
The text was updated successfully, but these errors were encountered:
Was reading the source code and noticed it actually breaks if the sync_interval in the configuration file is set to -1. Confirmed to work as expected. So, feature already exists!
Use case
Running the container as a script, just execute a single cycle
Describe the solution you'd like
While the container could be up and running and set with whatever poll frequency desired, for my use-case the polling is infrequent and upon request really. I'd like to be able to run the container with a single sync cycle instead of polling. Maybe if it's set to 0 or something?
Describe alternatives you've considered
I could start the container upon request, and have it automatically stopped after a set amount of time that ensures a sync completes but no second sync is started. While it would work, it's not exactly an elegant solution.
The text was updated successfully, but these errors were encountered: