-
Notifications
You must be signed in to change notification settings - Fork 28
[propolis-server] pass in api-version header to migrate requests #958
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
Merged
sunshowers
merged 1 commit into
master
from
sunshowers/spr/propolis-server-pass-in-api-version-header-to-migrate-requests
Oct 10, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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 a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the tension here is that we don't want to always pick the latest version here, because that might be across a change to the HTTP API, but we probably don't want to always use
VERSION_INITIALhere so that we can drop support for ancientpropolis-serverHTTP APIs over time, right?does it make sense to suggest bumping this header if we've bumped the
propolis-serverAPI version without changing this endpoint? (am I off-base in thinking we'll probably want to keep code for the last like.. one or two API versions in-tree, but not beyond that?)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah no, the issue is if a new propolis-server with a newer version hits an old propolis-server without that version, the request will get rejected. So we'll always have to use a version that overlaps with the newest as well as the oldest propolis-server currently deployed.
The exact process of deprecation and removal of old versions is a TBD, but we'll have to consider circumstances like this. Wouldn't worry about it too much for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, right, so we'd move this version forward as we deprecate the oldest versions of the API. or something along those lines.