voxpupuli/puppet-elasticsearch 6.3.0

on GitHub

Migration Guide

Elasticsearch 6.3 includes several big changes that are reflected in this module.
When upgrading from module versions prior to 6.3, there are a number of upgrade considerations to take into account:

• This module defaults to the upstream package repositories, which now include X-Pack bundled by default. To preserve previous behavior which does not include X-Pack, follow the README instructions to configure oss-only repositories/packages.
  
  • Note that if your system was previously using the elasticsearch package and you instead choose to move to the oss distribution, the elasticsearch and elasticsearch-oss packages may conflict. If that occurs, consider ensuring that the elasticsearch package is absent before the ::elasticsearch class runs. This module does not explicitly remove the conflicting package to avoid unexpected package removal.
    
• Use of the elastic_stack::repo class for managing package repositories brings a couple changes:
  
  • All repository-level parameters and settings have been removed from the ::elasticsearch class. These parameters can now be set on the elastic_stack::repo class.
    
  • This may mean that leftover yum/apt/etc. repositories named elasticsearch may persist after upgrade.
    
• Some changes have been made to align this module's file-level permissions with upstream defaults on some configuration, data, and logging directories. Though these have been tested, operators should be aware that some permissions may change on-disk after upgrading to version >= 6.3.x of this module.
  

Features

• Added support for managing Elasticsearch licenses.
  
• This module now uses the elastic-stack module to manage package repositories.
  
• Supports OSS packaging distribution.
  
• X-Pack bundled with 6.3 support.
  

Fixes

• Ensure that the stock Elasticsearch service is not running.
  
• Service files for removed instances were previously set to ensure => absent on removal. Because this limits Puppet's ability to verify that the named service is running or not, these service files are always present now whether an instance is set to present or absent.
  
• The service defaults file now enforces user/group ownership inline with the service user runtime.
  
• The scripts configuration directory is now recursively copied instead of symlinked to avoid Elasticsearch security manager permission errors.
  
• X-Pack and other meta-plugins are now properly detected as installed by the native plugin provider.