[git-sync] about maxFailures... (with http status 429 Too many Requests from bitbucket)

[seunggabi]

https://community.atlassian.com/t5/Bitbucket-questions/git-sync-Too-many-requests-nfatal-unable-to-access-https/qaq-p/2461183#M96947

apache/airflow#33815

INFO: detected pid 1, running init handler
"level"=0 "msg"="starting up" "pid"=12 "args"=["/git-sync"]
"msg"="too many failures, aborting" "error"="Run(git ls-remote -q https://bitbucket.org/asdf/qwer.git refs/heads/stg): exit status 128: { stdout: "", stderr: "remote: Too many requests\nfatal: unable to access 'https://bitbucket.org/asdf/qwer.git/': The requested URL returned error: 429\n" }" "failCount"=0

Maybe bitbucket launched new policy (http status 429 Too many Requests from bitbucket).
(2023-08-25 23:16 KST)

So, My team changed gitSync.syncWait 5 -> 60 and considering applying maxFailures.
Because git-sync failures affect every component failures.

What value should I use for maxFailures?
I hope that if bitbucket requests fail, the entire component will not be affected.

I found related issue. but I am not confidence. apache/airflow#30268

dags:
  gitSync:
    maxFailures: -1 # never die..

it is good?..?