No problem exactly, but this may be an easier way to deploy ksconf by just assuming that we should use the embedded python2.7 and put all the dependencies in directly in the splunk package.
Describe the solution you'd like
It would be cool to have a UI interface, eventually but that would take some effort. A really simple roadmap that I just made up could look something like this:
Bundle ksconf in an app with all the python bits figured out. Users would add the app's bin folder to their path and run it from the CLI, as they do now. (Mostly this is a packaging convenience )
Add one or more SPL commands to interface to ksconf. (Read-only commands) This would allow users to potentially have visibility into their
Add more SPL commands to handle non-read only ksconf stuff. Possibly a rest interface? (Not sure if that's needed. Think more about it.)
Add a proper UI to allow the user to do "promote" style work directly from SplunkWeb and create (and possibly push) new commits.
NOTE: Getting approved for Splunk Cloud could be a challenge, but as-is cloud is completely off the table so this at least opens the door.
How serious are you about this change?
I'm not. Just an idea for now. Letting it brew.
Additional information
There's a serious risk of end-user confusion with this type of repackaging: Is it a CLI tool? Is it a SPL command? What does this app do? Does the app replace the python package? ... This could be really confusing for new users. So clarity is pretty important.
Likely this should go into its own repo and import the kintyre-splunk-conf package into the Splunk app version.
lowell80
commented
5 years ago
Is your feature request related to a problem?
No problem exactly, but this may be an easier way to deploy
ksconfby just assuming that we should use the embedded python2.7 and put all the dependencies in directly in the splunk package.Describe the solution you'd like
It would be cool to have a UI interface, eventually but that would take some effort. A really simple roadmap that I just made up could look something like this:
NOTE: Getting approved for Splunk Cloud could be a challenge, but as-is cloud is completely off the table so this at least opens the door.
How serious are you about this change?
I'm not. Just an idea for now. Letting it brew.
Additional information
There's a serious risk of end-user confusion with this type of repackaging: Is it a CLI tool? Is it a SPL command? What does this app do? Does the app replace the python package? ... This could be really confusing for new users. So clarity is pretty important.
Likely this should go into its own repo and import the
kintyre-splunk-confpackage into the Splunk app version.