Skip to content

Should we remove file-based scripts and templates? #21798

@clintongormley

Description

@clintongormley

We have largely removed support for file-based configuration (eg mappings, settings, index templates) in favour of storing this info in the cluster.

For scripts and mustache templates, we allow them to be passed inline or to be stored in the cluster state. We used to be concerned about locking down scripts in Groovy etc, but with Painless we have safe scripting. Are file based scripts now redundant?

The one upside of files is that scripts can be written with new lines and formatting, while with inline/stored scripts they have to be passed in in a single line of JSON with newlines escaped. However this could be solved by improving Console to do the multi->single line conversion automatically.

Any other reasons for keeping file scripts?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions