feat: Project Update API to wait for call to the Core #1695
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.
This PR modifies the Project Update API in a way that the call to update project metadata in the Core is not done asynchronously but synchronously. With the change, eventual problems on the Core side will be reported to the caller.
Another change regards projects with protected branches that Core cannot push to. In such cases, Project Update API returns
Conflict 409
status and updates only GL and TS but only with values that don't have to be passed to the Core. The values that need calling the Core are pushed by the Core to a new branch about the user is informed and for which the user needs to create a PR and merge it. An example response in this case will be: