[ENH] CMEK support in Python and JS client

[Sicheng-Pan]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • N/A
• New functionality
  • CMEK support in Python and JS client

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Migration plan

Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?

Observability plan

What is the plan to instrument and monitor this change?

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[Sicheng-Pan]

• [ENH] CMEK support in Python and JS client #5991 👈 (View in Graphite)
• [ENH] Add CMEK to collection schema #5975
• [ENH] Log service CMEK support #5971
• [ENH] Compactor CMEK support #5964
• [ENH] Update PutOptions #5953
• [ENH] CMEK support in storage #5949
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[propel-code-bot]

Add CMEK abstractions and schema plumbing to Python and JS clients

Introduces a cross-language Cmek abstraction with provider and resource handling, enabling schema-level CMEK configuration in both the Python and JavaScript clients. Extends schema serialization/deserialization, CLI exports, and unit tests to ensure CMEK data round-trips correctly while preserving existing index configuration behavior.

Key Changes

• Added Cmek dataclass and supporting enums/validation to chromadb/api/types.py, including schema serialization/deserialization hooks and warning-based error handling.
• Updated Schema class to carry an optional CMEK, expose set_cmek, and emit CMEK state during JSON conversions while maintaining index configuration semantics.
• Mirrored CMEK provider/serialization logic in the TypeScript client (schema.ts) with new warning logging and unit coverage.
• Expanded Python and JavaScript schema tests to cover CMEK creation, serialization round-trips, and interaction with existing index configuration tests.
• Re-exported Cmek from chromadb/__init__.py for public API availability.

Affected Areas

• chromadb/api/types.py
• chromadb/test/api/test_schema.py
• clients/new-js/packages/chromadb/src/schema.ts
• clients/new-js/packages/chromadb/test/schema.test.ts
• chromadb/init.py

This summary was automatically generated by @propel-code-bot

[propel-code-bot]

[Maintainability] This line is redundant. instance.cmek is already initialized to None before the if block and will retain that value if an exception is caught. You can safely remove this line to make the except block more concise.

Suggested change

	except (ValueError, KeyError) as e:
	warnings.warn(
	f"Could not deserialize CMEK configuration: {e}. Setting to None."
	)
	instance.cmek = None
	except (ValueError, KeyError) as e:
	warnings.warn(
	f"Could not deserialize CMEK configuration: {e}. Setting to None."
	)

Context for Agents

This line is redundant. `instance.cmek` is already initialized to `None` before the `if` block and will retain that value if an exception is caught. You can safely remove this line to make the `except` block more concise.

```suggestion
            except (ValueError, KeyError) as e:
                warnings.warn(
                    f"Could not deserialize CMEK configuration: {e}. Setting to None."
                )
```

File: chromadb/api/types.py
Line: 2570