Clean up elkstack's workarounds, java, deps #141
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- The lumberjack protocol will no longer be the default for Logstash to communicate, due to hosted chef changes and golang runtime SSL changes (fixes #56, #14) - Don't test the lumberjack protocol with the server install by default, removes lumberjack test suite in .kitchen.yml - Default to tcp/udp for communication between logstash instances, add flag: `node['elkstack']['config']['agent_protocol'] = 'tcp_udp' # could also be lumberjack` - Don't try to load lumberjack secrets by default for agent, don't fail if they aren't present (rename recipes/_secrets.rb -> recipes/_lumberjack_secrets.rb) - elkstack::acl recipe changes to support tcp/udp communication - add logstash configs for tcp/udp communication - remove tests for lumberjack.key/crt now from default test suites - remove extra data bags with lumberjack keypairs
- Fixes #135, stop making a distinction between a cluster install vs. a single all-in-one install without any agent. - Merge default and cluster and single recipes. Default is now a clustered elkstack. - Tags and search/discovery all operate off 'elkstack' tag. There is no more 'elkstack_cluster' tag. - Fixed some of the rspec/chefspec unit tests as well.
- Many dependencies have since been fixed and/or released to Supermarket.
- Fixes #138, stop shipping Java wrappers. You must include `java::default` or get Java some other way.
- Remove the kibana.yml workaround, now that kibana works again out of the box.
schwing
added a commit
that referenced
this pull request
May 4, 2015
Clean up elkstack's workarounds, java, deps
martinb3
added a commit
that referenced
this pull request
May 13, 2015
- Add additional guards for chef-solo before calling elasticsearch::search_discovery - Ensure node.deep_fetch is used when getting unicast hosts, handle empty / not found case - RE: #141.
martinb3
added a commit
that referenced
this pull request
May 13, 2015
- Add additional guards for chef-solo before calling elasticsearch::search_discovery - Ensure node.deep_fetch is used when getting unicast hosts, handle empty / not found case - RE: #141.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
java::defaultor get Java some other way.node['elkstack']['config']['agent_protocol'] = 'tcp_udp' # could also be lumberjack