Linode support #144
Linode support #144
Conversation
qdm12
force-pushed
the
linode
branch
4 times, most recently
from
47c7190
to
0a0cfdf
Compare
internal/settings/linode.go
Outdated
| } | ||
| r.Header.Set("Content-Type", "application/json") | ||
| r.Header.Set("Authorization", "Bearer "+l.token) | ||
| r.Header.Set("oauth", "domains:read_only") |
There was a problem hiding this comment.
I may be mistaken, but given we're using a personal access token, I don't think we need to define oauth headers?
There was a problem hiding this comment.
Hey thanks for the review 👍
That's what they have on their documentation.
You can probably define tokens with different kind of permissions.
It might not work if you don't precise which permission you want, but I can't test it for sure, I don't have an account 😉
There was a problem hiding this comment.
Sounds good! When creating the token, I had to assign permissions to it, but better to go with what the documentation says :)
There was a problem hiding this comment.
Oh interesting which permissions? Are these the same as in the code? So I can add these to the Linode documentation.
There was a problem hiding this comment.
Go to setting and API Tokens:
API Tokens Tab:
Add Personal Access Token.
I have a token with domains set, with read and write privileges, set to never expire
qdm12
force-pushed
the
linode
branch
2 times, most recently
from
a87609a
to
a9928d0
Compare
Fixes #143