Tomáš Karásek

project_id missing from Connection API resource

2

While wokring on Fabric Service Token support in the provider, I realized it's not possible to find out project ID from existing Dedicated Connection API resource. Connection resource is created...

There don't seem to be a href for API keys in EM API: ```json "api_keys": [ { "id": "baff8dfa-2053-4644-8592-e2bc63909da8", "token": "REMOVED", "created_at": "2016-11-17T11:43:39Z", "updated_at": "2016-11-17T11:43:39Z", "description": "tomk", "user": { "href":...

Support for network types per bond, and for the new hybrid-bonded type

1

Fixes #231 @displague will probably not be happy about the format of this PR, but I think this is the best way to add support for network type per bond...

Creating a Spot Market Request for a plan not available in a facility succeeds

1

Example: I create a SMR for 2 c3.small.x86 devices in ewr1 over the API (with packngo). c3.small.x86 is not available in ewr1 (I think it's not a matter of capacity,...

Our default facility for acceptance tests is "ny5". However ``` 422 Storage feature is not currently available in facility ny5 ``` .. so it's necessary to prefix call of tests...

When converting network type of n2.xlarge device from Hybrid to Layer2-bonded, it sometimes happen that the API returns HTTP success, but the network type of the bond interface is not...

Pagination

8

partially done in #64, #87 Paginated resources must have the List method modified to sth like `List(..., lo *ListOptions)`. In the ListOptions struct, user can specify what page, and per_page...

Device API resources reported with wrong network_type [caching?]

16

Maybe network_type caching again? I create a device in ewr1. It provisions and gets to `active` state. Then, sometimes, it's network_state is reported as `layer2-bonded` over the API and `layer3`...

API wrongly reports `Facility can't be blank` when device plan is unavailable, and when facility list doesn't contains a valid facility slug

4

When creating device over the API, and passing more than one facility (for failover), if a desired plan is not available in either of the facilities, the API responses with...

At the moment, the godoc for Packngo doesn't read very well: https://godoc.org/github.com/packethost/packngo This would need improving the comments in the code, and add some summary, like in https://github.com/gorilla/websocket/blob/master/doc.go And then...