[18.0][IMP] fs_storage: Makes the cache policy of fsspec client configurable#487
Conversation
On the fs.storage model you can now specify if the fsspec client must be cached into the ormcache once instanciated or not. By default, the filesystem is cacheable but in some cases, like when using OAuth2 authentication, the filesystem cannot be cached because it depends on the user and the token can change.
lmignon
force-pushed
the
18.0-fs-folder-no-orm-cache
branch
from
b42dff9 to
cfa306a
Compare
|
/ocabot merge patch |
|
On my way to merge this fine PR! |
|
@lmignon your merge command was aborted due to failed check(s), which you can inspect on this commit of 18.0-ocabot-merge-pr-487-by-lmignon-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
|
/ocabot merge patch |
|
On my way to merge this fine PR! |
|
It looks like something changed on |
|
Congratulations, your PR was merged at 3e27f0d. Thanks a lot for contributing to OCA. ❤️ |
2 participants
On the fs.storage model you can now specify if the fsspec client must be cached into the ormcache once instanciated or not. By default, the filesystem is cacheable but in some cases, like when using OAuth2 authentication, the filesystem cannot be cached because it depends on the user and the token can change.