Skip to content

Plugin resource's plugin_dir should have a sensible default #345

@michaelklishin

Description

@michaelklishin

README examples and even code comments use usr/local/awesome/elasticsearch-version/plugins as a plugin_dir value. I'm not sure if that's a real world example or not. Surely ElasticSearch provides a standard plugins directory: why doesn't this cookbook have a default for that? Why do the users have to even think about where to put the plugins?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions