Ryan Wynn

you should be able to. can you try using the api key authentication? https://github.com/rwynn/monstache/issues/589 https://www.elastic.co/guide/en/cloud-enterprise/current/ece-restful-api-authentication.html

For others, the configuration option is `elasticsearch-api-key`. This just hasn't been added to the docs yet.

You can explicitly associate an existing pipeline to an index request from monstache using a `mapping` configuration. https://rwynn.github.io/monstache-site/config/#pipeline An alternative is to use this feature if you version of Elasticsearch...

Hi @yasha-wibbitz thanks and happy to hear it's been useful! 1. Connection errors at startup should be causing the container to exit. How much time that takes is controlled by...

Hi @itswadesh I just pinned the issue with instructions for Elasticsearch 8 support for more visibility. https://github.com/rwynn/monstache/issues/657 Let me know if you have any issue with the instructions.

We have some workaround for transactions, but I don't think for multiple updates in the same transaction. https://github.com/rwynn/monstache/issues/552

If you understand the implications of not sending a version number with each indexing request, you can enable this setting https://rwynn.github.io/monstache-site/config/#index-as-update

This may actually already be working as intended to ensure you do not overwrite the data in Elastic with a previous version. https://www.elastic.co/blog/elasticsearch-versioning-support

Is there any reason you enabled `enable-oplog = true`? That is an option to support legacy versions of MongoDB before change streams were introduced in 3.6. It issues queries directly...

You can actually remove that 1 result restriction with ```toml disable-delete-protection = true ``` It would then delete any document that matches the search and not restrict it to 1...