controller/ER file watcher strange behavior

[ekoby]

on macOS with HA: 3 controllers, 1 ER running

1. it appears to trigger file watcher event for unrelated files:

[  45.803]    INFO identity.(*ID).queueReload.func1: reloading identity configuration
[ 427.432]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: CREATE        "kc1.json"
[ 427.432]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: CREATE        "sample_enroll"
[ 427.432]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: CREATE        "ziti"
[ 427.432]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: CREATE        "ziti-prox-c"
[ 427.432]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: CREATE        "ziti_mfa"
[ 427.433]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE|CHMOD   "kc1.json"

2. some events put file watcher in a busy loop (for all controllers and ER):

[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""
[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""
[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""
[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""
[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""
[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""
[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""
[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""
[ 509.968]    INFO identity.(*ID).startWatching.func1: identity file watcher received event, queuing reload: WRITE         ""

I was able to trigger it by creating an identity and enrolling it (new jwt and json file) in this directory