Rewritten elasticsearch::template using native type and provider. Fixed and added additional proxy parameters to elasticsearch::plugin instances. Exposed repo priority parameters for apt and yum repos. This release removes that environment variable, which could potentially change path.
Take proper precautions when upgrading to avoid unexpected downtime or data loss test module upgrades, et cetera. Rewritten yaml generator, code cleanup, and various bugfixes. Configuration file yaml no longer nested. Service no longer restarts by default, and exposes more granular restart options.
Summary This releases adds several important features and fixes an important plugin installation issue with ES 1. We reverted the change that implemented the full 40 character for the apt repo key.
This caused issues with some older versions of the puppetlabs-apt module. Summary This is the first bug fix release for 0. A bug was reported with the recursive file management. Summary This release is the first one towards 1. Our planning is to provide LTS releases with the puppet module. Summary This release introduces instances to facilitate the option to have more then a single instance running on the host system.
PuppetEcosystem Puppet Community Updates. Any Supported Supported or Approved. Operating system Any. With tasks?
Any Yes. Module for managing and configuring Elasticsearch nodes. Module Stats 3,, downloads 35, latest version 5. Version information 6. This version is compatible with: Puppet Enterprise Start using this module. Installation method r10k or Code Manager.
Add this module to your Puppetfile: mod 'elastic-elasticsearch', '6. Add this module to your Bolt project: bolt module add elastic-elasticsearch. Manually install this module globally with Puppet module tool: puppet module install elastic-elasticsearch --version 6.
Elasticsearch Puppet Module Table of Contents Module description - What the module does and why it is useful Setup - The basics of getting started with Elasticsearch The module manages the following Requirements Usage - Configuration options and additional functionality Advanced features - Extra information on advanced usage Reference - An under-the-hood peek at what the module is doing and how Limitations - OS compatibility, etc.
Development - Guide for contributing to the module Support - When you need help with this module Module description This module sets up Elasticsearch instances with additional resource for plugins, templates, and more. This module is actively tested against Elasticsearch 2. Setup The module manages the following Elasticsearch repository files.
Elasticsearch package. Elasticsearch configuration file. Elasticsearch service. Elasticsearch plugins. Elasticsearch snapshot repositories. Elasticsearch templates. Elasticsearch ingest pipelines. Elasticsearch index settings. Elasticsearch licenses. Elasticsearch keystores. Requirements The stdlib Puppet library.
Usage Main class Most top-level parameters in the elasticsearch class are set to reasonable defaults. Automatically restarting the service default set to false By default, the module will not restart Elasticsearch when the configuration file, package, or plugins change. Dynamically Created Resources This module supports managing all of its defined types through top-level parameters to better support Hiera and Puppet Enterprise.
Plugins This module can help manage a variety of plugins. Scripts Installs scripts to be used by Elasticsearch. Creating an index At the time of this writing, only index settings are supported.
Roles Roles in the file realm the esusers realm in Shield can be managed using the elasticsearch::role type. Data directories There are several different ways of setting data directories for Elasticsearch.
Shared global data directories In some cases, you may want to share a top-level data directory among multiple instances. Main and instance configurations The config option in both the main class and the instances can be configured to work together.
Overriding When duplicate options are provided, the option in the instance config overrides the ones from the main class. Reference Class parameters are available in the auto-generated documentation pages.
Limitations This module is built upon and tested against the versions of Puppet listed in the metadata. Support Need help? Types in this module release Expand all. Manages elasticsearch service files. Manages an Elasticsearch keystore settings file. Provider for elasticsearch-keystore based secret management.
The port that the Elasticsearch instance should be listening on. Manages Elasticsearch ingest pipelines. Manages Elasticsearch index settings.
Type to model Elasticsearch users. Manages Elasticsearch licenses. Type to model Elasticsearch roles. Plugin installation type. Manages Elasticsearch index templates. Type to model Elasticsearch user roles. Manages Elasticsearch snapshot repositories. Type to model Elasticsearch role mappings. 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. Some changes have been made to align this module's file-level permissions with upstream defaults on some configuration, data, and logging directories.
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. Fixes Ensure that the stock Elasticsearch service is not running.
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 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. Fixes Rewrote the exists?
This fundamentally changes how the module detects the presence of plugins but should be backwards compatible. Brought some options in jvm. Package pinning is no longer supported. Java installation is no longer supported.
The python and ruby defined types have been removed. Minor: elasticsearch::plugin only accepts present or absent Some REST-resource based providers such as templates and pipelines now validate parameters such as numeric port numbers more rigorously. The following migration guide is intended to help aid in upgrading this module.
Migration Guide Puppet 3. Package Pinning No Longer Supported Package pinning caused lots of unexpected behavior and usually caused more problems than solutions. Java Installation No Longer Supported Java installation was a very simple operation in this module which simply declared an instance of the java class but created conflicts for users who managed Java separately.
Removal of Python and Ruby Resources These resource types were simple wrappers around package resources with their providers set to pip and gem , respectively. Automatic Package Repository Management This parameter is now set to true by default to automatically manage the Elastic repository.
Both the logging. Plugins with colon-delimited names such as maven plugins are properly handled now. Fixed a bug that would cause dependency cycles when using parameters to create defined types. Features Failures are no longer raised when no instances are defined for a plugin and service restarts are not requested. Fixes log4j template now properly respects deprecation logging settings.
The elasticsearch::script type now supports recursively managing directories of scripts. All module defined types can now be managed as top-level hash parameters to the elasticsearch class primarily for hiera and PE Fixes Fixed a bug that prevented plugins from being updated properly. Fixed deprecated default. Fixes This is a hotfix release to support users affected by an upstream Elasticsearch issue. Minor bugfixes. Features Ingestion pipelines supported via custom resources. Index settings support.
Fixes Custom facts no longer fail when trying to read unreadable elasticsearch config files. Accept and Content-Type headers properly set for providers to support ES 6.
Summary Note that this is a major version release! Backwards-Incompatible Changes The elasticsearch::shield::user and elasticsearch::shield::role resources have been renamed to elasticsearch::user and elasticsearch::role since the resource now handles both Shield and X-Pack. If you previously managed Shield resources with version 0. The first changes that may be Elasticsearch 1. This only impacts version 1. Features Support management of the global jvm.
X-Pack support added. Restricted permissions to the elasticsearch. Deprecation log configuration support added. Synced systemd service file with upstream. Bugfixes Fixed case in which index template could prepend an additional 'index.
Fixed a case in which dependency cycles could arise when pinning packages on CentOS. Unused defaults values now purged from instance init defaults files. Calls to elasticsearch -version in elasticsearch::plugin code replaced with native Puppet code to resolve Elasticsearch package version.
Should improve resiliency when managing plugins. Testing changes 0. Initial support for running Elasticsearch 5. Features Support management of 5. Support service scripts for 5. Bugfixes Permissions on the Elasticsearch plugin directory have been fixed to permit world read rights. Fixed a broken File dependency when a plugin was set to absent and ::elasticsearch set to present. Fixed issue when using the proxy parameter on plugins in Elasticsearch 2. Numerics in elasticsearch.
Features Plugin installation for the 5. Bugfixes Recursively enforce correct plugin directory mode to avoid Elasticsearch startup permissions errors. Fixed an edge case where dependency cycles could arise when managing absent resources. Bugfixes Fixed systemd elasticsearch.
Resources are now explicitly ordered to ensure behavior such as plugins being installed before instance start, users managed before templates changed, etc. Changes Updated repository gpg fingerprint key to long form to silence module warnings. The elasticsearch::config parameter now supports deep hiera merging. Bugfixes Content of templates should now properly trigger new API PUT requests when the index template stored in Elasticsearch differs from the template defined in puppet.
Installing plugins with proxy parameters now works correctly due to changed Java property flags. Changes The file parameter on the elasticsearch::template defined type has been deprecated to be consistent with usage of the source parameter for other types. Summary Rewritten yaml generator, code cleanup, and various bugfixes.
Bugfixes Special yaml cases such as arrays of hashes and strings like "::" are properly supported. This was an undocumented parameter that often caused problems for users. The elasticsearch. Package pinning is now contained within a separate class, so users can opt to manage package repositories manually and still use this module's pinning feature.
All configuration hashes are now flattened into dot-notated yaml in the elasticsearch configuration file. This should be fairly transparent in terms of behavior, though the config file formatting will change. Testing changes The acceptance test suite has been dramatically slimmed to cut down on testing time and reduce false positives.
This caused issues with some older versions of the puppetlabs-apt module Features Bugfixes Revert using the full 40 character for the apt repo key. Our planning is to provide LTS releases with the puppet module Features Support for using hiera to define instances and plugins.
Support for OpenSuSE Features Rewrite module to incorperate multi instance support New readme layout Bugfixes None Changes Adding ec2-linux osfamily for repo management Retry behaviour for plugin installation Testing changes Adding Puppet 3.
Add ability to use stage instead of anchor for repo class Minor fixes to system tests 0. Increase time for retry to insert the template 0. This caused issues when using our logstash module Add spec tests for plugin define 0. Apache License Version 2. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link or bind by name to the interfaces of, the Work and Derivative Works thereof.
For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution.
Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable except as stated in this section patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution s alone or by combination of their Contribution s with the Work to which such Contribution s was submitted.
If You institute patent litigation against any entity including a cross-claim or counterclaim in a lawsuit alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
The backup command requires a running Elasticsearch instance and the path to a folder where the dumps will be written to. The restore command requires a running Elasticsearch instance and the path to a folder where the dumps were written to by the previous backup command.
For example, you can restore the previously saved indices by executing the command and pointing to the dump folder, with. In addition, an upgrade of the Siren Investigate indices is also executed after a successful restore. To upgrade the objects in the. It is possible to run the command multiple times, however running the command at the same time from multiple machines is not supported. The upgrade command runs an automatic backup of the siren indices. Siren Platform User Guide.
Prev Next. Upgrading to Elasticsearch version 6. Note Before you upgrade, read the 8. Backup the. Download and extract the new Siren Investigate version.
Check for breaking changes to the configuration. Upgrading from a previous version If you are running Elasticsearch 5. Note Elasticsearch requires a matching version of Search Guard. In this section :.
0コメント