-
Notifications
You must be signed in to change notification settings - Fork 5
Authentication headers aren't being sent with coreapi 2.3.0, but 2.2.4 works #19
Comments
Authentication works fine when using coreapi-cli and CoreAPI version |
Same bug on |
I degraded coreapi to 2.2.4, and coreapi-cli is 1.0.6. But I still get error of "TypeError: init() missing 1 required positional argument: 'enum'". Any idea? Thanks. I degraded coreapi to 2.0.0, it works |
|
@blueyed Thanks! @tomchristie It would be awesome if you could have a look into this... atm any coreapi-generated doc will point to use the coreapi client and this is broken 📦 |
I can confirm this happens with: coreapi==2.3.3 @blueyed @tomchristie any chance we can get this fixed? |
@pau-minoves |
hi @blueyed I just tried and I still have the problem. I see that pull request fixes some warnings but not actual logic. Am I right? |
@pau-minoves |
Make sure to actually use the branch/PR with coreapi-cli when testing it. |
@blueyed right, I can confirm that branch works. Thanks! Any change it gets merged into a regular coreapi release? |
Waiting for the fix on the For now, downgrading coreapi worked for me:
|
@bradleyglen Thanks, I can confirm that. With |
There is a pending fix already at core-api/python-client#146 - no need to confirm this over and over again. |
@tomchristie Thank you ++ |
The CLI doesn't seem to correctly use coreapi's authentication anymore with the latest coreapi libary.
If I use coreapi cli 1.0.6 and coreapi 2.0.0, the authentication header is being sent (Not my real creds or domain):
But if I switch to the latest coreapi 2.3.0, it doesn't get sent:
For the moment, I'm just reverting to coreapi 2.0.0 as a workaround.
The text was updated successfully, but these errors were encountered: