[HDDS-1357] ozone s3 shell command has confusing subcommands

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.4.1
• Labels: pull-request-available
• Target Version/s: 0.4.0
• Sprint: Done
• Assignee: Marton Elek
• Reporter: Marton Elek
• Created: 29/Mar/19 15:06
• Updated: 05/Aug/19 14:45
• Resolved: 30/Mar/19 17:21

Description

Let's check the potential subcommands of ozone sh:

[hadoop@om-0 keytabs]$ ozone sh
Incomplete command
Usage: ozone sh [-hV] [--verbose] [-D=<String=String>]... [COMMAND]
Shell for Ozone object store
      --verbose   More verbose output. Show the stack trace of the errors.
  -D, --set=<String=String>

  -h, --help      Show this help message and exit.
  -V, --version   Print version information and exit.
Commands:
  volume, vol  Volume specific operations
  bucket       Bucket specific operations
  key          Key specific operations
  token        Token specific operations

This is fine, but for ozone s3:

[hadoop@om-0 keytabs]$ ozone s3
Incomplete command
Usage: ozone s3 [-hV] [--verbose] [-D=<String=String>]... [COMMAND]
Shell for S3 specific operations
      --verbose   More verbose output. Show the stack trace of the errors.
  -D, --set=<String=String>

  -h, --help      Show this help message and exit.
  -V, --version   Print version information and exit.
Commands:
  getsecret    Returns s3 secret for current user
  path         Returns the ozone path for S3Bucket
  volume, vol  Volume specific operations
  bucket       Bucket specific operations
  key          Key specific operations
  token        Token specific operations

This list should contain only the getsecret/path commands and not the volume/bucket/key subcommands.

Issue Links

• links to: GitHub Pull Request #663