Marques Johansson

Thinking about how this might work in Terraform, I think if someone asks for "hybrid-bonded", we may have to ignore "layer3-bonded", because it is the same but they don't have...

> Or maybe just use layer3 and attach VLANs. VLAN assignment can already be done from Packngo, and also from the TF provider. In this TF case we would have...

> Is this even feasible when the API will change? AFAIK, the API is not changing other than the new reported mode "hybrid-bonded", which is effectively a Layer3 port (as...

@t0mk supporting documentation for this feature is now available at https://metal.equinix.com/developers/docs/layer2-networking/hybrid-bonded-mode/

@t0mk Perhaps we should take this one-line https://github.com/packethost/packngo/pull/239/files#diff-e9a0f6f206a7d5bf4e4fb40ffcdf7089c3223878283915d8d03f2175727515dcR5 (adding the hybrid-bonded state) and make an enum of it for `type PortNetworkType string`. Here's a snippet of the packngo JSON serialization...

I don't know what this is. We can reopen if this is important. Looks like PR spam to me.

I believe `POST /organizations/{id}/connection` does not require a `project_id` for Dedicated connections. If packngo offered a second function or logic to change endpoints based on project_id being specified then Terraform...

> What level of version change will this introduce? Playing devil's advocate for a moment, we are still in `0.` version land. We could just introduce the leading context parameter....

Filed an internal ticket, thanks.

While trying to reproduce this, I encountered somewhat similar, when passing multiple facilities and one is incorrect (nyc5 instead of ny5 in this case): ``` {"errors":["[\"ewr1\", \"nyc5\"] is not a...