packet, a CLI tool to manage Packet services

packet is a CLI tool to manage packet.net services. You can browse the help here.

    .--~~~~~~~~~~~~~------.
   /--===============------\\
   | |^^^^^^^^^^^^^^^|     |
   | |               |     |
   | | > packet      |     |
   | |               |     |
   | |_______________|     |
   |                   ::::|
   '======================='
   //-"-"-"-"-"-"-"-"-"-"-\\\\
  //_"_"_"_"_"_"_"_"_"_"_"_\\\\
  [-------------------------]
  \\_________________________/

Installation

Install with go get

$ go get -u github.com/ebsarr/packet

packet executable will be installed in $GOPATH/bin

You can also run it in a docker container:

$ docker run -it ebsarr/packet bash

Try the help

$ packet -h
CLI tool to manage packet.net services

Usage:
  packet [flags]
  packet [command]

Available Commands:
  admin           Manage projects, ssh keys, etc...
  baremetal       Manage server devices.
  network         Manage packet network services
  storage         Manage your storages

Flags:
  -k, --key string       API key
  -p, --profile string   Profile name (default "default")
  -v, --version          Show version and exit

Use "packet [command] --help" for more information about a command.

Getting started

Configure your API key by adding a profile

Command syntax: packet admin add-profile

$ packet admin add-profile
Enter your API key [ *****y7wi ]: <APIKEY>
Enter your default project ID [  ]: <Project ID>

This command will add a profile named "default".
NOTE: Without your API key configured, you'll need to specify it in every command in the form: packet --key <APIKEY> <command> <subcommand> <flags>. You can also optionnaly configure a default project ID.

If you have multiple accounts, or if you are working on multiple projects, you can set profiles to make it easy to switch between accounts or projects. After setting multiple profiles, you can use -p or --profile option to switch between accounts and projects.

Setting a profile

Here I'm creating a new profile named ebsarr

$ packet admin add-profile -n ebsarr
Enter your API key [ *****y7wi ]: <APIKEY>
Enter your default project ID [  ]: <Project ID>

Without the -n switch, the add-profile command sets up a profile named "default". You can view your profiles with the list-profiles command:

$ packet admin list-profiles
NAME      	APIKEY                          	DEFAULT PROJECT
----      	------                          	---------------
default   	XMiR----------------------------	13935598-d08c-4bd8------------------
ebsarr    	XMiR----------------------------	e30d25da-728d-47fe------------------

Now I can switch easily between projects when running the packet command:

$ packet -p ebsarr baremetal list-devices
[]

Without the -p option, the default profile will be used:

$ packet baremetal list-devices
[
    {
        "id": "69148e7c-44e1-4b4a-ac1a-f9e08b552fe8",
        "href": "/devices/69148e7c-44e1-4b4a-ac1a-f9e08b552fe8",
        "hostname": "ebsarrtest01",
        "state": "active",
        "created_at": "2016-07-15T07:16:28Z",
        "updated_at": "2016-07-15T07:31:27Z",
        "billing_cycle": "hourly",
        "ip_addresses": [
...

Available commands

packet admin : project management

Syntax: packet admin [subcommand]

packet baremetal: Manage server devices

Syntax: packet baremetal [subcommand]

packet network: Manage packet network services

Syntax: packet network [subcommand]

packet storage: manage your storages

Syntax: package storage [subcommand]
Some of the snapshot related commands may not make sense. I will revisit the API and correct this on the next update.

For more help

Type packet -h in your console or browse the help here to view command options.

License

Changelog