-
-
Notifications
You must be signed in to change notification settings - Fork 616
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
Feature Request: Have an auto update ttl for downloaded taskfiles #1402
Comments
Hihi, I'm wondering if I can take a shot at implementing something here to help out. @andreynering @pd93 any notes? 🙏 |
Hi @jlucktay. You're welcome to give this a go. This should probably be implemented in the Taskfile cache. Adding a TTL to that struct and then checking the files last modified time. or possibly adding a timestamp to the cached filename? The OP says that they'd like to change the default behaviour to use the cache first (instead of using the remote first). However I think this is outside the scope of the TTL work and is a separate decision that needs to be made before remote Taskfiles are made generally available. I don't think that setting a TTL by itself should modify this behaviour. |
Mapped out a flowchart to describe the behaviour of taskfile.Cache, so as to aid technical design and implementation. re go-task#1402
Thanks for the steer! I sketched out a flowchart on my fork's branch and will see how I go getting something built. |
Mapped out a flowchart to describe the behaviour of taskfile.Cache, so as to aid technical design and implementation. re go-task#1402
Mapped out a flowchart to describe the behaviour of taskfile.Cache, so as to aid technical design and implementation. re go-task#1402
Mapped out a flowchart to describe the behaviour of taskfile.Cache, so as to aid technical design and implementation. re go-task#1402
As discussed here, it would be great to have an auto-cache-ttl setting for downloaded taskfiles.
Context:
I am wanting to use the remote features to have a standard set of taskfile includes across my org.
For me, I would like it to download first, then by default always use the cache. I run taskfile a lot, (multiple times a minute if I'm running a debugging command like
task test -- feature/a
), so having extra network overhead wouldn't be useful.I understand that there is work on on offline flag, but using that would mean my taskfiles would need manual updating.
Having some kind of auto-update-ttl would allow users to have the fast latency of not fetching every task run, but also allow automatic updates in a soft manner.
Thanks for all your hard work on this great tool!
The text was updated successfully, but these errors were encountered: