You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
autocreatealways 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_existsalways defaults to true - unlike autocreate - unless overridden in config.php
The text was updated successfully, but these errors were encountered:
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 inconfig.php
)autocreate
always defaults tofalse
in the Object Stores that support itverify_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 toautocreate
with one major exception (last item below)verify_bucket_exists
behaves similarly toautocreate
(it creates the bucket if it doesn't already exist)verify_bucket_exists
always defaults to true - unlikeautocreate
- unless overridden inconfig.php
The text was updated successfully, but these errors were encountered: