You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
I setup canopy. I get an error at 'canopy new'. The reason is because it tries to create a server somewhere besides my region, and to upgrade my plan. The guide on the github page says Starter Plan works for this; I don't understand.
Error: Failed to create a new index. Reason:
Failed to create index canopy--test due to error: {"error":{"code":"INVALID_ARGUMENT","message":"Bad request: Your free plan does not support indexes in the us-west-2 region of aws. To create indexes in this region, upgrade your plan."},"status":400}
I suspect Pinecone uses AWS for storage, and aws-west is not free. It seems that aws-east is.
This solved the error for me:
Find the config.yaml in canopy/config_templates/ (this may be in your virtual environment folder, depending on your setup)
Copy this file. Rename and store wherever it suits your project setup
Find region: us-west-2 and set the value to us-east-1
From the terminal, type export CANOPY_CONFIG_FILE="path/to/your/config.yaml". This adds your config file as an environment variable. Now when you do canopy new, canopy will detect the config file.
Root cause
I see the default spec in kb.create_canopy_index specifies "us-west-2":
Is this a new bug?
Current Behavior
I setup canopy. I get an error at 'canopy new'. The reason is because it tries to create a server somewhere besides my region, and to upgrade my plan. The guide on the github page says Starter Plan works for this; I don't understand.
Expected Behavior
A canopy enabled index would be created.
Steps To Reproduce
Relevant log output
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: