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
Copy file name to clipboardExpand all lines: docs/NooBaaNonContainerized/AccountsAndBuckets.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,9 @@ See all available account properties - [NC Account Schema](../../src/server/syst
38
38
39
39
-`new_buckets_path` - When an account creates a bucket using the S3 protocol, NooBaa will create the underlying file system directory. This directory will be created under new_buckets_path. Note that the account must have read and write access to its `new_buckets_path`. Must be an absolute path.
40
40
41
-
-`custom_bucket_path_allowed_list` - When an account creates a bucket using the S3 protocol, He can override the default bucket path location (under new_buckets_path) using `x-noobaa-custom-bucket-path` HTTP header. This directory will be created only if this path will be under one of the provided allowed list paths in custom_bucket_path_allowed_list. Must be a list of absolute paths (divided by colons).
41
+
-`custom_bucket_path_allowed_list` - When an account creates a bucket using the S3 protocol, He can override the default bucket path location (under new_buckets_path) using `x-noobaa-custom-bucket-path` HTTP header. This directory will be created only if this path will be under one of the provided allowed list paths in custom_bucket_path_allowed_list. Must be a list of absolute paths (divided by colons).
42
+
43
+
-`allow_bypass_governance` - Give permission to the user to bypass governance-mode retention object lock, allowing them to set the `x-amz-bypass-governance-retention` header for deleting the object and modifying retention lock. See https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html#object-lock-retention-modes
42
44
43
45
### Account configuration
44
46
Currently, an account can be configured via NooBaa CLI, see - [NooBaa CLI](./NooBaaCLI.md).
Copy file name to clipboardExpand all lines: src/manage_nsfs/manage_nsfs_help_utils.js
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -144,6 +144,7 @@ Flags:
144
144
--iam_operate_on_root_account <true | false> (optional) Set the account to create root accounts instead of IAM users in IAM API requests.
145
145
--from_file <string> (optional) Use details from the JSON file, there is no need to mention all the properties individually in the CLI
146
146
--custom_bucket_path_allowed_list <string> (optional) Set the list of allowed custom bucket paths, separated by colons (:) example: '/gpfs/data/custom1/:/gpfs/data/custom2/'
147
+
--allow_bypass_governance <true | false> (optional) Set the account to allow bypassing governance mode object lock for object deletion and retention configuration (unset with '')
147
148
`;
148
149
149
150
constACCOUNT_FLAGS_UPDATE=`
@@ -172,6 +173,7 @@ Flags:
172
173
--force_md5_etag <true | false> (optional) Update the account to force md5 etag calculation (unset with '') (will override default config.NSFS_NC_STORAGE_BACKEND)
173
174
--iam_operate_on_root_account <true | false> (optional) Update the account to create root accounts instead of IAM users in IAM API requests.
174
175
--custom_bucket_path_allowed_list <string> (optional) Update the list of allowed custom bucket paths, separated by colons (:) example: '/gpfs/data/custom1/:/gpfs/data/custom2/' (override;unset with '')
176
+
--allow_bypass_governance <true | false> (optional) Update the account to allow bypassing governance mode object lock for object deletion and retention configuration (unset with '')
* @param {boolean} bypass_governance - if true, and user has permission to use this flag, will allow to bypass governance mode retention lock. compliance mode retention lock cannot be bypassed.
2324
2328
* @throws {S3Error.AccessDenied} if the object is protected by object lock and the user does not have permission to bypass the lock
* @param {boolean} bypass_governance - if true, and user has permission to use this flag, will allow to bypass governance mode retention lock. compliance mode retention lock cannot be bypassed.
2350
2354
* @throws {S3Error.AccessDenied} if the object is protected by object lock and the user does not have permission to bypass the lock
0 commit comments