Using VPC Service via CLI

Introduction

BCE CLI accesses VPC services using VPC subcommands to manage resources like VPCs, subnets, and routes.

CLI uses a multi-layer command structure. All commands start with bce, where [options] represents the options supported by BCE CLI, and <service> represents the services supported by CLI (such as BOS and CDN). Each service has multiple specific sub-commands.

1$ bce [options] [<service> <command> [parameters [options]]]

Parameter explanation

General options for CLI

• View help: Add -h or --help after any command to view help information for that command.

  Plain Text Copy

  1$ bce -h
  2$ bce vpc -h
  3$ bce vpc list-vpc --help

• View/set configuration information (AK, SK, etc.): -c/--configure

  Plain Text Copy

  1$ bce -c [<conf-path>]

• View version information: -v/--version

  Plain Text Copy

  1  $ bce -v

• View debug information: -d/--debug

  Plain Text Copy

  1  $ bce -d vpc list-vpc

This -d/--debug command cannot be used independently and must be combined with the service.

• Use a specified configuration file: --conf-path

  Plain Text Copy

  1  $ bce --conf-path ./conf-sample/ vpc list-vpc

If --conf-path command is not used, the configuration in the user’s home directory ~/.bce is used by default.