Cisco-AMP / amp4e_splunk_events_input

BSD 2-Clause "Simplified" License
8 stars 12 forks source link

Fix creating and editing inputs #73

Closed pschulze closed 2 years ago

pschulze commented 2 years ago

Input creation was failing when there was no user named admin on the Splunk instance. This changes the owner of the input to nobody.

Should (hopefully) fix #67 #48 #30

Additionally, adds safe navigation operators to the API key check to fix JS failures when attempting to edit inputs.

PR check to run tests is on the fritz, here's the result of running them locally:

~/repos/amp4e_splunk_events_input  develop ✗                                                                                    3m ⚑  
▶ docker-compose exec splunk sh -c '$SPLUNK_HOME/bin/splunk cmd python -m unittest discover' 
........................................
----------------------------------------------------------------------
Ran 40 tests in 3.835s

OK
kvaratop commented 2 years ago

hi @pschulze @samsnguy @samsonnguyeI I have the same problem about "Please wait" infinity message on "New input" page. image

image

And it is not resolved by this fix=( Please, help!

-amp4e_events_input logs: Received response from ApiService (200) -firewall: there are "allow" ACLs for 443 to amp.eu.... -splunk version 8.2.3

p.s: in the local test via docker all is working fine!