Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persist min/max supported protocol versions by a service endpoint #1508

Merged
merged 5 commits into from
May 16, 2024

Conversation

tillrohrmann
Copy link
Contributor

This commit validates and persists the reported min/max protocol version
for a service endpoint in the DeploymentMetadata.

This fixes #1507.

Copy link
Contributor

@slinkydeveloper slinkydeveloper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to add the accept header in the request, and check the response contains a supported content-type header too.


Suggestions:

* Check the compatibility matrix between SDK and server versions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could definitely use a page in the documentation for that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once we have it, we can link it from this error.

crates/errors/src/error_codes/META0012.md Outdated Show resolved Hide resolved
crates/service-protocol/build.rs Show resolved Hide resolved
crates/service-protocol/build.rs Outdated Show resolved Hide resolved
crates/service-protocol/src/discovery.rs Outdated Show resolved Hide resolved
@tillrohrmann
Copy link
Contributor Author

You need to add the accept header in the request, and check the response contains a supported content-type header too.

This isn't implemented in this PR and will be done by a follow-up PR.

@tillrohrmann
Copy link
Contributor Author

Thanks for your review @slinkydeveloper. I've addressed your comments and pushed an update. PTAL.

…361ef..1898426f

1898426f Update min/max of protocol version fields in endpoint_manifest_schema
08871e0b Introduce service.Version and discovery.Version enums
2f3e461f Workflow api changes (restatedev#91)
1fa71a5b Add versioning info (restatedev#90)

git-subtree-dir: crates/service-protocol/service-protocol
git-subtree-split: 1898426fc98c16d704068594cd54394912845ff7
This commit validates and persists the reported min/max protocol version
for a service endpoint in the DeploymentMetadata.

This fixes restatedev#1507.
Most likely, a DiscoveryError::BadResponse is caused by an
incompatible service endpoint.
@tillrohrmann tillrohrmann merged commit 772fac6 into restatedev:main May 16, 2024
5 checks passed
@tillrohrmann tillrohrmann deleted the issues/1507 branch May 16, 2024 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Store min/max version from discovery manifest in schema registry
2 participants