-
Notifications
You must be signed in to change notification settings - Fork 75
VersionLocalState in sync with VersionSummary + Activation/Deactivation timestamps #585
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
Conversation
// aip.dev/not-precedent: 'Since' captures the field semantics despite being a preposition. --) | ||
google.protobuf.Timestamp ramping_since_time = 6; | ||
// Last time `current_since_time`, `ramping_since_time, or `ramp_percentage` of this version changed. | ||
google.protobuf.Timestamp routing_update_time = 7; |
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.
nit: last_routing_update_time
for clarity?
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.
Thanks for the suggestion! Hmm, I still am leaning towards routing_update_time
since the word 'update' already implies the latest change, so adding last_ felt a bit redundant to me.
Not making this change right now, but let me know if you still feel strongly about this.
READ BEFORE MERGING: All PRs require approval by both Server AND SDK teams before merging! This is why the number of required approvals is "2" and not "1"--two reviewers from the same team is NOT sufficient. If your PR is not approved by someone in BOTH teams, it may be summarily reverted.
What changed?
WorkerDeploymentVersionInfo
andWorkerDeploymentInfo
.Added missing fields from VersionLocalState that were not present in VersionSummary.
Why?
VersionLocalState
were added to theVersionSummary
is because the UI, right now, is querying a bunch of different places to get information about a specific version. This might be annoying and the aim of this PR is to make VersionSummary the source of truth for information related to a specific version. A nice cherry on top is that this shall also reduce the number of API calls to get information about a version.Breaking changes
Server PR