Would it be possible to improve the types for the listSearchIndexes, so we can have the correct type definitions? Currently, it just returns {name: string}.
Thanks for reporting this issue @Alex_Bjorlig. I’ve filed NODE-5611 to improve this behavior.
1 Like
I did think about opening a JIRA issue, but it feels more comfortable here ![]()
Btw - I have implemented a flow that defines Atlas search indexes in version control, and syncs to Atlas if there are changes on each deployment. Works great ![]()
