Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

elasticsearch_configure provider should not modify default resource parameters #445

Closed
martinb3 opened this issue Mar 22, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@martinb3
Copy link
Contributor

commented Mar 22, 2016

The elasticsearch_configure provider is currently writing to new_resource.default_configuration:

    if new_resource.path_conf[es_install.type] && new_resource.default_configuration['path.conf'].nil?
      new_resource.default_configuration['path.conf'] = new_resource.path_conf[es_install.type]

This isn't a problem when only creating a single resource, but if subsequent resources of the same type are defined, they are receiving the modified new_resource.default_configuration value, and then have a bunch of unexpected settings from the previous resource.

This is causing issues for people who run more than one instance, e.g. #444.

@martinb3 martinb3 closed this in a140bf5 Mar 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.