I just use dynamic groovy scripts which are acceptable because they are sandboxed. If the sandbox is too restrictive you can carefully loosen it using configuration.
Nik On Wed, Oct 29, 2014 at 10:08 AM, Deryk Wenaus <de...@bluemandala.com> wrote: > I've upgraded to Elasticsearch 1.3.x and by default dynamic scripting is > disabled for security reasons. The advice is now to place any used scripts > as a file in config/scripts directory. My question is how to integrate this > into a multi-user production environment? Each developer needs to have it > installed, the circleci needs it, I have to ensure the search cluster > connected to Heroku has it. Is there anyway I can integrate this into our > git workflow? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/e75bcf24-60b1-49bb-a6b4-7fe302938d81%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/e75bcf24-60b1-49bb-a6b4-7fe302938d81%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0i0TuWqsgZvzyhCk8spR_28R8p5jX4PUG%2BVjeUh6yzNA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
