Stop overriding default jvm.options file

[jmlrt]

This role is currently using jvm.options.j2 template to override the default config/jvm.options file provided by Elasticsearch package.

Maintaining this template to keep default options from the file provided by Elasticsearch package for every version while allowing to change some specific options is really painful.

Since 7.7.0, Elasticsearch allow to add override options in config/jvm.options.d/ and instead of modifying default config/jvm.options.

Adding support for it in ansible-elasticsearch role would allow us to remove the jvm.options.j2 template and use the default options file provided by Elasticsearch instead while allowing more flexibility in what users can override.

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic]

This issue has been automatically closed because it has not had recent activity since being marked as stale.

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.