This is problematic in 4.3.2 as you mentioned, but in 4.3.3 and going forward, there is a parameter (check-index) that you can set to make this to happen without getting an error message complaining about the nonexistent index. By setting check-index to false, Universal Forwarder would not require the index to be there to begin with, but this is not the default behavior in 4.3.3.
For example:
./splunk add monitor /var/log/case1 -index test_case1 -check-index false
The default behavior is different depending on the version
4.3.3 universal forwarder: default check-index is true, which means that it would always check whether the index exists
4.3.4 universal forwarder: default check-index is true, which means that it would always check whether the index exists
4.3.5 universal forwarder: default check-index is true, which means that it would always check whether the index exists
5.0.2 universal forwarder: default check-index is false
... View more