Marques Johansson

Outside of this patch, on the Device `customdata`, I observed in the `PACKNGO_DEBUG` output that a `POST {"customdata": "{\"foo\":\"bar\"}"}` will result in a `GET` of `{"customdata": {"foo": "bar"}}`. It would...

@t0mk definitely a concern. We would need for `PUT` requests to be able to omit `customdata` when no change is requested, and still be able to overwrite existing values with...

Thanks, @t0mk. I think we'll be able to refer to this table as we continue to build CustomData support and we can certainly refer users here for specific needs. I...

Noting that this is related to #221 which added CustomData for IPReservation resources.

I stumbled upon https://golang.org/pkg/encoding/json/#RawMessage and wondered if this might be a type to use in our CustomData fields.

Project.CustomData should also be exposed. Upon revisiting this issue,`json.RawMessage` seems to be the best approach, allowing for all JSON types without the ambiguity of `interface{}`.

The context provided here is to support the implementation and downstream implementations. Validation should be left to the API service, packngo should not try to verify if the current state...

@t0mk That had not crossed my mind. We did benefit from console.equinix.com front-end Javascript in https://github.com/packethost/packngo/pull/185 and it would be great to sync that again here. The UI code doesn't...

I checked with another internal composition of this field. The new hybrid-bonded computed value has these requirements: * all ports are bonded * it has any ip management addresses *...

Transitioning to Hybrid-Bonded, would not be possible without a VLAN to attach, but it would otherwise be the same as transitioning to Layer3 Bonded.