Marques Johansson

@invidian @deitch It sounds like this has been resolved on the Gardner side. Reopen if there is more to investigate.

Similarly, Terraform can currently report a 422 during an unassign: ``` Error: POST https://api.equinix.com/metal/v1/ports/d628ab1d-c7e4-49b4-b8fa-405a8a2a3b8c/unassign: 422 Virtual network 1353 not assigned ```

I've been going back and forth between wether or not packngo should act as a transparent HTTP client or an intelligent arbiter of intent. The Terraform client, for example, can...

I'm aware that this kind of logic would be harder to bake into a generated client, in that case I think we would introduce helper packages or functions that add...

Updating this issue with some developments over the past two years. A good bit of experimentation has happened at https://github.com/t0mk/gometal. Here @t0mk and I collaborated on [go-swagger](https://github.com/go-swagger/go-swagger) and then [openapitools](https://github.com/OpenAPITools/openapi-generator/)...

If we use release-drafter, we will need a job in that workflow that runs just before release-drafter to do the version bump. While we are at it, we could change...

Since #281, we don't need to update the version stored in version.go. This means that tags can be applied at any time, using the GH UI. Release automation would be...

Are the debug messages Terraform flavored or are they only from `PACKNGO_DEBUG` (Equinix Metal API requests and responses)?

Terraform has its own request/response debugging capabilities. This may not be packngo related at all. The formatting can reveal which tool is producing the output. https://github.com/packethost/packngo/blob/master/packngo.go#L265-L303

Is this during tests? I can't find the issue, but I believe there is a Terraform issue around excessive logging (I think this was during tests). It might help to...