I am trying to run the singer-io

tap-github

and struggling to submit an authorized request. I can access private data via Postman and curl with

curl --request GET '<https://api.github.com/repos/immuta/my-private-repo/commits|https://api.github.com/repos/immuta/bodata/commits>' \
--header 'authorization: token <mytoken>'

. But I get a "not authorized" when adding the header via requests / the tap. what's more is that it looks like requests is adding its own

Basic

authorization to the request payload instead of honoring the passed-in token. Has anyone seen this before?

import requests

resp = requests.get(
    "<https://api.github.com/repos/immuta/my-private-repo/commits>",
    headers={"Authorization": "token foo"},
)

print(resp.request.headers)

> {'User-Agent': 'python-requests/2.22.0', 'Accept-Encoding': 'gzip, deflate', 'Accept': '*/*', 'Connection': 'keep-alive', 'Authorization': 'Basic L1VzZXJzL25vdG91Y2gtaG90c3BhcmU6L1VzZX5vdG91Y2gtaG90c3BhcmU='}

The basic authorization toekn, decoded, is

my-mac-user:my-mac-user

🤨 Where is that coming from??

You said this is the

singer-io

fork, right? No, I haven't seen anything like that.

Yeah, it seems to be doing this: https://github.com/singer-io/tap-github/issues/112

@stephen_bailey I've not tried accessing private repos, as my focus on this project is purely opensource. That said, I've had quite a few hiccups with the

singer-io

tap, and so decided to bite the bullet and move over to the

MeltanoLabs

one instead. I am adding in the streams that I need, but overall the foundations are A LOT stronger.

Yes! That’s what I love about the SDK. No need to put on your adventure hat when going into a new repo

interesting!

thats one word for it 🙃