-
Notifications
You must be signed in to change notification settings - Fork 9
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
Regenerate client code for 2024-10
#86
Regenerate client code for 2024-10
#86
Conversation
pinecone/client.go
Outdated
PodCount: int32(idx.Spec.Pod.Pods), | ||
Replicas: idx.Spec.Pod.Replicas, | ||
ShardCount: idx.Spec.Pod.Shards, | ||
PodCount: derefOrDefault(idx.Spec.Pod.Pods, 0), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think these should ever realistically be nil
when coming back from the server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree... maybe the default should be 1 (as that's the count if all other defaults are used)
pinecone/client.go
Outdated
PodCount: int32(idx.Spec.Pod.Pods), | ||
Replicas: idx.Spec.Pod.Replicas, | ||
ShardCount: idx.Spec.Pod.Shards, | ||
PodCount: derefOrDefault(idx.Spec.Pod.Pods, 0), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree... maybe the default should be 1 (as that's the count if all other defaults are used)
## Problem PR was merged today making some slight adjustments to the db control spec to better align with the server impl: pinecone-io/apis#181 ## Solution Slightly adjust the `PodSpec` type and related code to account for the new shape. ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [ ] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan `just test` - CI
Problem
PR was merged today making some slight adjustments to the db control spec to better align with the server impl: https://github.com/pinecone-io/apis/pull/181
Solution
Slightly adjust the
PodSpec
type and related code to account for the new shape.Type of Change
Test Plan
just test
- CI