"lw cloud network public list" doesn't filter out private

[sgsullivan]

ssullivan@data2 ~ $ lw cloud network public list --uniq-id 2T79JD
IP Assignments for 2T79JD:
        IP: 50.28.34.90
                Id: 1210289
                Gateway: 50.28.32.1
                Broadcast: 50.28.35.255
                Netmask: 255.255.252.0
                Network: 255.255.252.0
        IP: 10.30.200.62
                Id: 1210650
                Gateway: 10.30.200.1
                Broadcast: 10.30.207.255
                Netmask: 255.255.248.0
                Network: 255.255.248.0
        IP: 50.28.34.72
                Id: 1210855
                Gateway: 50.28.32.1
                Broadcast: 50.28.35.255
                Netmask: 255.255.252.0
                Network: 255.255.252.0
ssullivan@data2 ~ $ 

[dwburke]

instead of filtering, what about labeling / identifying it as private?

[sgsullivan]

The reason i was leaning towards filtering, was because of this scenario:

ssullivan@data2 ~ $ lw cloud network private details --uniq-id 2T79JD
Cloud Server is attached to a Private Network
        IP: 10.30.200.62
        Legacy: false
ssullivan@data2 ~ $ lw cloud network public list --uniq-id 2T79JD
IP Assignments for 2T79JD:
        IP: 50.28.34.90
                Id: 1210289
                Gateway: 50.28.32.1
                Broadcast: 50.28.35.255
                Netmask: 255.255.252.0
                Network: 255.255.252.0
        IP: 10.30.200.62
                Id: 1210650
                Gateway: 10.30.200.1
                Broadcast: 10.30.207.255
                Netmask: 255.255.248.0
                Network: 255.255.248.0
        IP: 50.28.34.72
                Id: 1210855
                Gateway: 50.28.32.1
                Broadcast: 50.28.35.255
                Netmask: 255.255.252.0
                Network: 255.255.252.0
ssullivan@data2 ~ $ 

So we have a lw cloud network private and a lw cloud network public pattern going on atm. That said, perhaps there could be a better way to present this.

[dwburke]

ah, I see

[sgsullivan]

probably wouldn't be a bad idea to change lw cloud network private details to lw cloud network private list to match lw cloud network public list

[sgsullivan]

decided to just clearly label it as private #52