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

Versioning for node-split #340

Open
Tracked by #338
pigmej opened this issue Jan 30, 2025 · 0 comments
Open
Tracked by #338

Versioning for node-split #340

pigmej opened this issue Jan 30, 2025 · 0 comments

Comments

@pigmej
Copy link
Member

pigmej commented Jan 30, 2025

Given the "only api integrations" we need to re-introduce versions to the APIs.

The current idea would be to have two separate versions served as:

  • v2beta1.NodeService/Version
  • v2beta1.SmesherService/Version

We split them because we may split the binaries even further in the future, so there will need to be two separate calls.

The version should return stuff similar to v1 API, so it should be a version (tag) and a commit.

Additionally after the backends are done we need to have some frontend integration for it too where based on the returned SmeshingService version proper frontend is served.

@pigmej pigmej changed the title Backend versioning for node-split Versioning for node-split Jan 30, 2025
@pigmej pigmej mentioned this issue Feb 7, 2025
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant