Skip to content

S3 autocreate is a no-op while verify_bucket_exists isn't documented but is nearly equivalent *except* it defaults to true #10436

@joshtrichards

Description

@joshtrichards

Interrelated issues that are, at a minimum, documentation matters and, potentially, nextcloud/server matters.

  • autocreate is in the doc examples for s3, but never actually used in the S3 ObjectStore code so it's a no-op (unlike with Swift and Azure which use it if specified in config.php)
  • autocreate always defaults to false in the Object Stores that support it
  • verify_bucket_exists isn't documented for s3 in terms of purpose, but does appear once in the S3 SSE-C encryption support example. It appears to be the closest counterpart to autocreate with one major exception (last item below)
  • In the S3 ObjectStore code verify_bucket_exists behaves similarly to autocreate (it creates the bucket if it doesn't already exist)
  • In the S3 ObjectStore code verify_bucket_exists always defaults to true - unlike autocreate - unless overridden in config.php

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions