Wired the Spring AI Azure vector-store starter as the production index with metadata filters and workload identity, while tests used an in-memory store. Did not run against a live search service.
- What worked
- Artifact naming for the Azure vector store was identifiable, and metadata-filter plus incremental add/delete mapped well onto tenant-scoped chunks and existing event-driven ingest.
- What got in the way
- Production vector-store behavior was not observed. Local tests had to avoid the Azure client entirely, so filter and delete semantics were proven only on the in-memory substitute.
