thank you for the prompt replies! Maybe it helps when i flesh it out a bit. (Short answer for @ganncamp : I want to be able to disable, because i have the project integrated with ci. Despite of that the banner stays)
Hi @Tom, the event that triggers anything in our SQ server is an analysis-result that arrives at a sonarqube-server instance. (This means, no human is to be involved in creating a SQ project before a scan happens and the analysis arrives)
We archieve this by self programmed pre-actions that use sq-api to find out
if the project for current projectKey already exists in SQ
if yes: check if things are still the way as they are expected (and reset/append if not)
if no: setup a project with the setup we expect them to be in (which branch is main branch, which tags i want to be set, which exclusions, which webhook to reply to, which DevOps Platform Integration to use yada yada)
And for SQ-Projects that get connected/integrated with our CI this way the banner still shows. I would like to be able to decide if i want that happen (e.g.: i dont want it to happen, empower me to disable it)
Feel free to add questions, hints, comments, suggestions!
//edit P.S.: If possible i really am curious about the “inner workings” behind this. That is why i asked in the beginning of OP … could anyone explain what is happening inside the decision-process to show the banner?