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.

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

azureblob: allow working with only list+create/write permissions (fix no_head_object/add no_read_for_metadata) #7813

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Commits on Apr 30, 2024

  1. azureblob: allow working with only list+create/write permissions (fix…

    … no_head_object/add no_read_for_metadata)
    
    There are three reasons an option why one would avoid HEAD requests on azureblob, with this now mainly implementing the latter one:
    
    - no_head_object: Don't do a HEAD *before* writing to (or reading from) an object, to reduce the number of transactions and thus increase performance. **This already exists in azureblob, a small issue was fixed here where using a prefix would still require a HEAD request to the prefix itself.**
    - no_head: Don't do a HEAD *after* writing to an object, for the same reason but at the cost of "increasing the chance for undetected upload failures".  **This is still not implemented for azureblob yet and quite complex, see s3.Object.Update()!**
    - no_read_for_metadata: Instead of doing a HEAD to get metadata, use a list operation, to avoid requiring READ permissions for immutable/append-only applications (this seems to be quite azureblob-specific) - one could also use both no_head_object and no_head together to achieve this, but then uploads wouldn't be verified.
    
    Fixes rclone#6162 and rclone#7027
    moqmar committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    839ca0e View commit details
    Browse the repository at this point in the history