fix token API not returning IDs anymore #86
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scaleway recently overhauled their token API - now there are a couple of changes:
access_key
andsecret_key
.ID
is no longer present in the response payload. It seems it has been deprecated in favor ofaccess_key
To make this a non-breaking change the SDK now sets the ID when reading with a specific ID.
Note that due to the API changes on Scaleway's side the tests are broken without this change.
All tests are green (together with #87)