Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Switch from 'cloudant' to 'ibmcloudant'
See original GitHub issueApache Airflow Provider(s)
cloudant
Apache Airflow version
main (development)
What happened
The IBM Cloudant API client we’re currently using, cloudant (aka python-cloudant), reached EOL last December. The authors recommend switching to ibmcloudant. The switch itself doesn’t seem too complicated (disclaimer: I have zero knowledge on IBM Cloudant), but ibmcloudant is depending on PyJWT<3.0.0,>=2.0.1, which conflicts to Flask-Appbuilder’s PyJWT<2.0.0,>=1.7.1. So we need to unblock either pacakge somehow to make this work.
See also dpgaspar/Flask-AppBuilder#1691
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project’s Code of Conduct
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Now that https://github.com/apache/airflow/pull/24399 is merged I believe this task is unblocked 😃 We will need however to set the provider with min version of Airflow 2.4.0
You need to ask Flask-AppBuilder. They cause the conflict, and if they don’t resolve it, Airflow cannot fix the issue.