Updating for version 7.1.1 #73
Open
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
updated for 6.6.1
fixed a few typos in build and publish scripts
All changes made to modify this to 6.6.2
stretch-slim, vs jessie
…ms to work with debian:jessie
Updated for splunk version 6.6.2
Update for splunk version 6.6.3.
6.6.3 splunk version. Images pushed to docker hub and splunk's registry.
Updated docker-compose to v3
6.6.3 updated with new docker-compose.yml info and README.md updates
Splunk 7.0.0
Splunk 7.0.1
Merge pull request splunk#61 from outcoldman/pr-7.0.1
Splunk 7.0.2
Splunk 7.1.0
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.
Updating the various build/publish/documentation files to reflect version 7.1.1. Any comments or suggestions are welcome!
Let me know if there's a different branching/merging structure folks would like me to use (I'm a little confused by the versioning that's merged into the master branch). @michaelwilde, as a member of the Splunk Github group, can you provide some insight?