fix(hc): Change RPC schemas to be represented as OpenAPI #68345
Closed
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.
Change RPC schemas that can't be represented in the OpenAPI format, generally because they rely on a fixed-length tuple with declared types at individual indexes. The success criterion is that the
sentry rpcschema --diagnose
command (not present in this branch, but can be merged locally from #68337) indicates 0 errors.Because this branch covers breaking changes both to services and call sites, it will not be deployed to production as-is. We will use the five-step procedure for rolling out breaking RPC changes. However, to avoid having to redo steps, I'm hoping to get it reviewed all at once. (Most of the RPC changes are mechanistic, but there are a few design choices in the model changes -- names and such.)
Here are the RPC services being changed and associated errors from
sentry rpcschema --diagnose
being fixed:I hope that's not too much to review at once. If it is, I could decompose it into separate PRs (but would then want to re-compose it for the sake of the five-step rollout process mentioned above, so yeah).