fix(worker): Permission syncer fixes #624
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes two issues:
userScopedPrismaClientExtensionin/web/src/prisma.tsand b) the/collaboratorsendpoint may not be accessible to the provided token. For example, consider this config:Assuming
GITHUB_TOKENis a fine-grained access token with access tosourcebot-dev, then this connection will sync with allpublicandprivaterepositories insourcebot-dev, and allpublicrepositories incodemirror. Previously, when thecodemirrorrepositories permissions were synced, we would hit 403s becauseGITHUB_TOKENis not scoped to thecodemirrororg.The other way of viewing this is that by filtering out public repositories during syncing, we are guaranteed that whatever repositories we do sync will have their
/collaboratorsendpoint accessible by the fact that they were accessible during connection syncing.force = trueoption toworker.closeto prevent this behaviour.