smengcl commented on issue #583: HDDS-3057. Improve Ozone Shell ACL operations' help text readability URL: https://github.com/apache/hadoop-ozone/pull/583#issuecomment-589925780 Manual test output, with fancy shell expansion: ## Command ```bash $ eval ozone\ sh\ {volume,bucket,key}\ {add,remove,set,get}acl\ -h\; ``` ## Results ### volume addacl ``` Usage: ozone sh volume addacl [-hV] -a=<acl> [-s=<storeType>] <uri> Add a new ACL. echo ozone\ sh\ {volume,bucket,key}\ {add,remove,set,get}acl\ -h\; <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -a, --acl=<acl> The new ACL to be added. Ex: user:user1:rw or group:hadoop:rw r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### volume removeacl ``` Usage: ozone sh volume removeacl [-hV] -a=<acl> [-s=<storeType>] <uri> Remove an existing ACL. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -a, --acl=<acl> The ACL to be removed. Ex: user:user1:rw or group:hadoop:rw r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### volume setacl ``` Usage: ozone sh volume setacl [-hV] -al=<acls> [-s=<storeType>] <uri> Set one or more ACLs, replacing the existing ones. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -al, --acls=<acls> A comma separated list of ACLs to be set. Ex: user:user1:rw,user:user2:a,group:hadoop:a r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` # volume getacl ``` Usage: ozone sh volume getacl [-hV] [-s=<storeType>] <uri> List all ACLs. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### bucket addacl ``` Usage: ozone sh bucket addacl [-hV] -a=<acl> [-s=<storeType>] <uri> Add a new ACL. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -a, --acl=<acl> The new ACL to be added. Ex: user:user1:rw or group:hadoop:rw r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### bucket removeacl ``` Usage: ozone sh bucket removeacl [-hV] -a=<acl> [-s=<storeType>] <uri> Remove an existing ACL. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -a, --acl=<acl> The ACL to be removed. Ex: user:user1:rw or group:hadoop:rw r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### bucket setacl ``` Usage: ozone sh bucket setacl [-hV] -al=<acls> [-s=<storeType>] <uri> Set one or more ACLs, replacing the existing ones. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -al, --acls=<acls> A comma separated list of ACLs to be set. Ex: user:user1:rw,user:user2:a,group:hadoop:a r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### bucket getacl ``` Usage: ozone sh bucket getacl [-hV] [-s=<storeType>] <uri> List all ACLs. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### key addacl ``` Usage: ozone sh key addacl [-hV] -a=<acl> [-s=<storeType>] <uri> Add a new ACL. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -a, --acl=<acl> The new ACL to be added. Ex: user:user1:rw or group:hadoop:rw r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### key removeacl ``` Usage: ozone sh key removeacl [-hV] -a=<acl> [-s=<storeType>] <uri> Remove an existing ACL. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -a, --acl=<acl> The ACL to be removed. Ex: user:user1:rw or group:hadoop:rw r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### key setacl ``` Usage: ozone sh key setacl [-hV] -al=<acls> [-s=<storeType>] <uri> Set one or more ACLs, replacing the existing ones. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -al, --acls=<acls> A comma separated list of ACLs to be set. Ex: user:user1:rw,user:user2:a,group:hadoop:a r = READ, w = WRITE, c = CREATE, d = DELETE, l = LIST, a = ALL, n = NONE, x = READ_ACL, y = WRITE_ACL. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ``` ### key getacl ``` Usage: ozone sh key getacl [-hV] [-s=<storeType>] <uri> List all ACLs. <uri> URI of the volume/bucket. Ozone URI could start with o3:// or without prefix. URI may contain the host and port of the OM server. Both are optional. If they are not specified it will be identified from the config files. -h, --help Show this help message and exit. -s, --store=<storeType> Store type. i.e OZONE or S3 -V, --version Print version information and exit. ```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
