Add a way to see private IP of the machine about doctl HOT 6 CLOSED

Lists both public and private IP list of all your DO droplets

doctl compute droplet list -o json |jq -r '.[]| "\(.id)\t\(.name)\t\(.networks.v4[].ip_address)"'

List them in single line

doctl compute droplet list -o json |jq -r '.[]| "\(.id)\t\(.name)\t\(.networks.v4[]|select(.type=="public")|.ip_address)\t\(.networks.v4[]|select(.type=="private")|.ip_address)"'

from doctl.

MacGyver solution combinding doctl access credentials, APIv2, and jq

curl -s -X GET \
    -H "Content-Type: text/plain" \
    -H "Authorization: Bearer $(awk '{print $2}' < ~/.doctlcfg)" \
    "https://api.digitalocean.com/v2/droplets/${machine_id}" | \
        jq -r '.droplet.networks.v4[] | select(.type=="private") | .ip_address'

from doctl.

Yes, only the public IPv4 address is easily accessible, but there is still a way:

 doctl compute droplet get <dropletID> -o json \
  | jq -c '.[].networks.v4[] | select(.type=="private").ip_address'

You don't need curl. The key points here is that every command has JSON output than you can mangle with jq

from doctl.

Right, missed the fact that doctl provides json output (see my temporary solution above).
Still, would be nice to just have that and not depend on external dependency like jq

from doctl.

I think ultimately we shouldn't hardcode every single thing in, but if doctl provided a a way to get at the raw JSON a bit easier, it wouldn't be too bad. Perhaps the easy way would be allow go template, and JSON path support, so you could do something like

doctl compute droplet get <dropletID> --go-template="whatever" or
doctl compute droplet get <dropletID> --jsonpath="whatever"

from doctl.

Created new issues to add these two features in #95 and #96.

from doctl.