Lag in getting Otterdog based repo configuration changes merged

Summary

During the last weeks I noticed that PRs for making changes to repository configuration using Otterdog tend to fail to be merged automatically or do not qualify as being eligible to be merged using a GitHub comment anymore. Mostly this seems to be due to the fact that the current configuration supposedly is not in sync with the jsonnet file that I try to change.

What is the current bug behavior?

When I create a PR, manual review by the EF security team is required, i.e. I have no chance to merge using a comment only. What makes it (much) worse is the fact, that the bandwidth of the EF security team seems to be quite limited. PRs sometimes take weeks to be reviewed/processed which is a real pity because it undermines the original intention of Otterdog to allow many changes to be applied by members of the project security team themselves, without the need for manual intervention from EF staff.

Relevant logs and/or screenshots

https://github.com/eclipse-uprotocol/.eclipsefdn/pull/90 https://github.com/eclipse-uprotocol/.eclipsefdn/pull/89#issuecomment-3253635269 https://github.com/eclipse-uprotocol/.eclipsefdn/pull/88#issuecomment-3223061987

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

In the worst case, each simple change that we want to make to repository configuration will require manual intervention from the EF security team. This will most likely lead to delays in our development and ability to deliver releases.