feat: project auth graph to be provisioned with visibility from GL #1676
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There was some uncertainty around the source of the project visibility info in the
MEMBER_SYNCflow that updates the newproject-authgraph. As it might be that theMEMBER_SYNCevent is processed before any data for the project exists in the TS, it seems safer not to reach for that to the TS but rather to the source which is GL. This PR modifies the flow to follow this logic.Additionally, there's an assumption taken that in case no visibility is found in GL, the project auth data in the new graph should be removed.