If I have the following scheme: <scheme> <title>My App</title> <description>Does stuff</description> <use_external_validation>true</use_external_validation> <use_single_instance>true</use_single_instance> <streaming_mode>xml</streaming_mode> <endpoint> <args> <arg name="MyArg"> <description>sample arg</description> <data_type>string</data_type> <required_on_edit>false</required_on_edit> <required_on_create>true</required_on_create> </arg> </args> </endpoint> And the following inputs.conf.spec [my_app://<name>] MyArg = <value> Using the appinspect API, The "Dynamic checks for modular inputs Modular Inputs are configured via an inputs.conf.spec file located at README/inputs.conf.spec" check fails claiming that "MyArg" defined in the scheme was not found in "README/inputs.conf.spec". If I change "MyArg" in the scheme to "myarg", the check passes. Why are the args in the spec file treated as case-insensitive when the check is run? When the app is installed in Splunk, Splunk treats the args in the spec file as case-sensitive. Shouldn't the behavior of the check be the same as Splunk? ... View more