tractus-x: "new" privilege to create repo variables and secrets manually clashes with Otterdog

Summary

(Summarize the bug encountered concisely)

Following up to the discussion in the this PR https://github.com/eclipse-tractusx/.eclipsefdn/pull/127#issuecomment-3022164237, I'd like to clarify what is recommended handling of repo variables and secrets.

I checked and it's not just project lead which have the privilege to add repo variables and secrets manually but also committers: https://github.com/eclipse-tractusx/bpdm/issues/1365#issuecomment-3031072747

I'm quite certain that for the longest time neither project leads nor committers could add repo variables and secrets manually due to missing privileges anyway, and seeing that we have that privilege now, that has changed at some point (recently?).

Should the option to add repo variables and secrets manually even be used if it clashes with Otterdog?

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")