The proposal here is to adjust the project matching logic to prompt user to choose the project if the active repo belongs to more than one projects in the Cloud/Enterprise.
User choice should be persisted (maybe?) for future sessions. And along with that we should provide command (e.g. Switch Project) to easily allow changing it.
And a bit of context:
Matching project is used to get policy and suppressions for active repo.
At the beginning we made some assumptions about matching local repository to remote project. It was done based on prChecks flag and if there was no project with such, first owner project of the repository will be used (also assuming that having repo in multiple projects is an edge case, or... maybe it wasn't possible back then 🤔).
At some point we deprecated prChecks flag for matching repos and so left with the logic matching first owner project of the repository.
And what we have now is not perfect. It came apparent when working with fingerprint suppressions that "kind of guessing project" we have now may be problematic and confusing, resulting also in unwanted suppressions in other projects.
We have partial workaround, which is monokle.project config, but it's not really user friendly.
The proposal here is to adjust the project matching logic to prompt user to choose the project if the active repo belongs to more than one projects in the Cloud/Enterprise.
User choice should be persisted (maybe?) for future sessions. And along with that we should provide command (e.g.
Switch Project) to easily allow changing it.And a bit of context:
Matching project is used to get policy and suppressions for active repo.
At the beginning we made some assumptions about matching local repository to remote project. It was done based on
prChecksflag and if there was no project with such, first owner project of the repository will be used (also assuming that having repo in multiple projects is an edge case, or... maybe it wasn't possible back then 🤔).At some point we deprecated
prChecksflag for matching repos and so left with the logic matching first owner project of the repository.And what we have now is not perfect. It came apparent when working with fingerprint suppressions that "kind of guessing project" we have now may be problematic and confusing, resulting also in unwanted suppressions in other projects.
We have partial workaround, which is
monokle.projectconfig, but it's not really user friendly.