mirror of
https://github.com/rclone/rclone.git
synced 2025-12-11 22:14:05 +01:00
f28c83c6de
Before this change, you had to modify a fragile data-structure containing all providers. This often led to things being out of order, duplicates and conflicts whilst merging. As well as the changes for one provider being in different places across the file. After this change, new providers are defined in an easy to edit YAML file, one per provider. The config output has been tested before and after for all providers and any changes are cosmetic only.
40 lines
1.2 KiB
YAML
40 lines
1.2 KiB
YAML
name: Other
|
|
description: Any other S3 compatible provider
|
|
region:
|
|
'': |-
|
|
Use this if unsure.
|
|
Will use v4 signatures and an empty region.
|
|
other-v2-signature: |-
|
|
Use this only if v4 signatures don't work.
|
|
E.g. pre Jewel/v10 CEPH.
|
|
endpoint: {}
|
|
location_constraint: {}
|
|
acl:
|
|
private: |-
|
|
Owner gets FULL_CONTROL.
|
|
No one else has access rights (default).
|
|
public-read: |-
|
|
Owner gets FULL_CONTROL.
|
|
The AllUsers group gets READ access.
|
|
public-read-write: |-
|
|
Owner gets FULL_CONTROL.
|
|
The AllUsers group gets READ and WRITE access.
|
|
Granting this on a bucket is generally not recommended.
|
|
authenticated-read: |-
|
|
Owner gets FULL_CONTROL.
|
|
The AuthenticatedUsers group gets READ access.
|
|
bucket-owner-read: |-
|
|
Object owner gets FULL_CONTROL.
|
|
Bucket owner gets READ access.
|
|
If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
|
|
bucket-owner-full-control: |-
|
|
Both the object owner and the bucket owner get FULL_CONTROL over the object.
|
|
If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
|
|
bucket_acl: true
|
|
quirks:
|
|
list_version: 1
|
|
force_path_style: true
|
|
list_url_encode: false
|
|
use_multipart_etag: false
|
|
use_already_exists: false
|