Migrate to Container-Based Testing and Add Host-Based Index Targeting #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR modernizes the Pinecone Ruby gem's testing infrastructure by migrating from VCR-based testing to local Pinecone containers and introduces host-based index targeting for improved performance.
🚀 Key Features
Host-Based Index Targeting (v1.2)
New recommended approach (faster)
client = Pinecone::Client.new
index = client.index(host: "my-index-abc123.svc.us-east1.pinecone.io")
Legacy approach (still works, but slower)
index = client.index("my-index-name") # Makes extra API call
Container-Based Testing Infrastructure
🔧 Technical Changes
API Enhancements
Test Infrastructure Overhaul
📊 Test Results
Before: Flaky VCR-based tests with external API dependencies
After:
🐳 Container Architecture
Data Plane (Vector Operations): Local Containers
Control Plane (Management): Strategic Mocking
🔄 Migration Path
Immediate Benefits:
Recommended Updates:
Before (slower)
index = client.index("my-index-name")
After (faster)
index = client.index(host: "my-index-abc123.svc.us-east1.pinecone.io")
🚦 CI/CD Integration
GitHub Actions now:
📈 Performance Impact
🔒 Backward Compatibility
📚 Documentation