Describe the bug
The local/inputs.conf information is not saved to the app that it belongs to. Rather, it saves the information in the app that splunk is currently open to (i.e. the search app). When I saved my configuration in the settings > input datas for my app I found the inputs.conf file was not created under my app. Searched with grep and I found the settings were saved in the splunk/etc/apps/search/local/inputs.conf
To Reproduce
Steps to reproduce the behavior:
Have the random_numbers example app installed and splunklib 2.0.1
Login to splunk and open the search app
Go to settings > data inputs > "add new" for "Random Number
Save settings
less $SPLUNK_HOME/etc/apps/search/local/inputs.conf
Expected behavior
Expected the inputs.conf to be saved in the app that it belongs to.
Splunk (please complete the following information):
Version: 9.1.3
OS: Debian 6.1
Deployment: Local VM, enterprise, free edition
SDK (please complete the following information):
Version: 2.0.1
Language Runtime Version: Python 3.7
OS: Debian 6.1
Additional context
Add any other context about the problem here.
Describe the bug The local/inputs.conf information is not saved to the app that it belongs to. Rather, it saves the information in the app that splunk is currently open to (i.e. the search app). When I saved my configuration in the settings > input datas for my app I found the inputs.conf file was not created under my app. Searched with grep and I found the settings were saved in the splunk/etc/apps/search/local/inputs.conf
To Reproduce Steps to reproduce the behavior:
Expected behavior Expected the inputs.conf to be saved in the app that it belongs to.
Splunk (please complete the following information):
SDK (please complete the following information):
Additional context Add any other context about the problem here.