ObjectRepositoryCachingLocalFs is not atomic

[sergiimk]

Describe the bug

ObjectRepositoryCachingLocalFs repo wrapper used to cache small S3 objects in the node writes to files in non-atomic way.

Steps To Reproduce

n/a

Current Behavior

A network error or an error during writing a file may result in a permanently corrupted file, breaking the node until cache is cleared or pod is restarted.

Expected Behavior

This wrapper should use the same strategy as ObjectRepositoryLocalFs - writing to a randomly named file first, and then performing atomic rename. Caching wrapper can actually use ObjectRepositoryLocalFs directly to avoid reimplementing this logic.

kamu system info

0.213.1

Logs

No response

Anything else?

No response