Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Error ignored when attempting to create an index on Starter plan in us-west-2 #104

Open
2 tasks done
jkodroff opened this issue Jul 4, 2024 · 0 comments
Open
2 tasks done
Labels
bug Something isn't working

Comments

@jkodroff
Copy link

jkodroff commented Jul 4, 2024

Is this a new bug?

  • I believe this is a new bug
  • I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Creating an index that is not permitted on the Starter plan gives a misleading error:

Expected Behavior

The error displayed in the console should be similar to what I found in the logs with pulumi up --logtostderr --logflow -v=10 2> out.txt:

I0704 10:39:10.254711    7060 eventsink.go:62] eventSink::Debug(<{%reset%}>Pinecone index creation response: {"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}<{%reset%}>)

From an API standpoint, if the error message give a link to explain the limitations and what region might be allowed, that would be great, but that's outside the scope of this repo.

The limitation on indices vs. billing plans should also be documented in the Pulumi Registry. (Just noting that there are limitations and pointing to a page in the Pinecone docs would be fine.)

Steps To Reproduce

  1. Ensure your default AWS region is us-west-2
  2. Run this repo against a Starter account: https://github.com/pinecone-io/aws-reference-architecture-pulumi?tab=readme-ov-file#quick-start-guide

Relevant log output

No response

Environment

- **OS**:
- **Language version**:
- **Pinecone client version**:

Additional Context

No response

@jkodroff jkodroff added the bug Something isn't working label Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant