-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
added technology addon feature #26
Conversation
I'd like to see some spec tests here, ensuring there is code coverage and things work as expected. |
# } | ||
# } | ||
# | ||
define splunk::ta ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this be easier understood if it was named splunk::addon
or something? "ta" isn't something I would know without reading docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or splunk::app
since it goes in the apps directory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! I think we don't require tests because there are none for the module at all, but if you could address my review comments that would be great! |
* splunk::ta renamed to splunk::addon * splunk::addon::input marked as private * template syntax clean up * concat for addon input made conditional to prevent blank file
@hunner thanks for looking this PR over... I agree with your points and I've modified the PR with a second commit that covers these. |
The splunk module has no support for configuring forwarders for TA's (technology addons) which, according to the docs, have their input forwarders configured in $SPLUNK_HOME/etc/apps//local/inputs.conf
I'm using a fork of this module to be able to have this feature - it currently only supports configuring inputs and installing packages for TA's but other local config could be added in the same model.
Would like to merge this to keep the upstream updated.