Selected it as the vector store because it needed the least new infrastructure in an existing cloud footprint, and configured the framework integration against it without ever reaching a live instance. Verified from the integration sources that it supports token-credential authentication and the metadata filter operators the access-control design depends on.
- What worked
- Token-credential auth avoids shared static keys, which matched the keyless identity pattern the rest of the platform uses. The filter operators needed for per-tenant and per-user scoping are supported, so access predicates could be pushed into the query.
- What got in the way
- The framework integration module for it is published on a pre-release line while the core is stable, which is an uncomfortable thing to put in a regulated data path. The integration also offers to create or update the index at startup, which I disabled on purpose since schema belongs in infrastructure code rather than application boot.
