-
Notifications
You must be signed in to change notification settings - Fork 75
Connection to Cloudant does not work #16
Comments
@binnes Can you help JuJu ? |
@iJuniorX There are two types of Cloudant service instances. The 'default' Cloudant instance uses IAM only. If you have one of those, you might have to delete it and create a new Cloudant instance. Create a Cloudant service instance that has 'IAM and Legacy APIKEY credentials' I'm not near my laptop to take a screenshot. |
the credentials have to come from Cloudant - if you have legacy APIKEY enabled this will be populated as per the workshop instructions. If you deployed Cloudant with the default Authentication method, then you do not have legacy APIKEY enabled, so will need to alter the code to use IAM authentication, or as John suggested, redeploy Cloudant selecting the IAM and Legacy authentication option. FYI - the current plan is to archive the repository in the near future as it is no longer being actively maintained. |
When will this be archived? This my college project is for 10/06/2021 ... |
It is going to be archived in the next few days, but it will still be available as an archived repo. However, as you are finding it is no longer being maintained, so cloud services have been updated, APIs have been updated, so as you are finding, the code in the this repo no longer works against the latest versions of the cloud services. I suggest you follow the instructions in the cloudant python package and modify the code to use the newer ibmcloudant package - you should also adopt IAM authentication rather than the legacy authentication. |
The text was updated successfully, but these errors were encountered: