Skip to content

Regenerate code from 2025-10, implement schema/read_capacity in BYOCSpec#614

Open
austin-denoble wants to merge 11 commits intomainfrom
adenoble/implement-byoc-metadata-and-drn
Open

Regenerate code from 2025-10, implement schema/read_capacity in BYOCSpec#614
austin-denoble wants to merge 11 commits intomainfrom
adenoble/implement-byoc-metadata-and-drn

Conversation

@austin-denoble
Copy link
Contributor

@austin-denoble austin-denoble commented Feb 11, 2026

Problem

When the Python client was released for 2025-10, the spec did not yet include BYOCSpec.read_capacity, so the ability to configure BYOC indexes with DRN is limited through the SDK.

Additionally, I noticed we never pulled in BYOCSpec.schema either, so that can be added in as well.

Solution

  • Regenerate core off of the 2025-10 spec to pull in most recent changes (make generate-oas). We shouldn't need to regenerate grpc for this as the changes are limited to BYOCSpec in the control plane.
  • Add support for schema and read_capacity to BYOCSpec, and make sure things are wired properly in request_factory.py.
  • Update references to BackupModelSchema to use MetadataSchema. This was due to an error in the spec wherein the MetadataSchema in the OpenAPI spec did not have an x-component-name. That was fixed here: https://github.com/pinecone-io/apis/pull/417. It's confusing to have BackupModelSchema used in all these areas that aren't backup-related.

Also pulled in some dependency bumps based on dependabot alerts:

aiohttp (2.6.3)

urllib3 (3.13.3)

filelock (3.21.0)

virtualenv (20.31.1)

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • 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

CI - unit, integration, etc


Note

Medium Risk
Touches generated API models plus request/response (de)serialization for index specs, so mismatches could surface at runtime when parsing spec/read_capacity payloads. Added tests reduce risk but changes affect core index management flows.

Overview
Updates codegen to the 2025-10 OpenAPI output and refreshes generated docs/comments (including index-management and vector fetch/query guidance).

Extends BYOC index support by adding read_capacity and schema wiring end-to-end: new ByocSpecResponse model, ByocSpec dataclass serialization, request factory parsing for BYOC read_capacity/schema, and IndexModel response deserialization fixes (manual oneOf handling + shared _deserialize_read_capacity, with relaxed type checking to avoid request/response type mismatches).

Renames the generated metadata schema types from BackupModelSchema* to MetadataSchema* across control-plane models and public interfaces, and expands unit/fixture coverage for schema parsing and BYOC/serverless read-capacity configuration; also tweaks a sparse-index error assertion and Ruff target-version to py310.

Written by Cursor Bugbot for commit 1976ce9. This will update automatically on new commits. Configure here.


…Schema to use MetadataSchema, add support for schema and read_capacity to BYOCSpec and make sure things are wired properly in request_factory.py
…ess and BYOC to remove duplication, fix bug when calling parse_non_empty_args for BYOC in __parse_index_spec, add unit tests to cover schema parsing logic
…deserializing spec in get_spec, update unit test to actually validate read_capacity
…xes, implement a unified helper for deserializing read_capacity generally and use in both places, add unit test fixture helpers for creating read_capacity, add unit tests to test_index_model.py
…port configuring read_capacity on both serverless and byoc indexes, add some unit tests to cover logic
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant