feat(sdk): regen — graph /metrics + /usage rename, instance resources#147
Merged
Conversation
Picks up the graph endpoint rename (robosystems #P0):
/v1/graphs/{graph_id}/analytics -> /v1/graphs/{graph_id}/metrics
/v1/graphs/{graph_id}/analytics/usage -> /v1/graphs/{graph_id}/usage
get_graph_metrics keeps its name — only its URL moved — so callers are
unaffected. get_graph_usage_analytics is renamed get_graph_usage; it had
no consumers.
DatabaseHealthResponse gains cpu_usage_percent, memory_usage_percent and
resource_status, and memory_usage_mb is now actually populated. All four
are only returned for dedicated single-tenant instances and are null on
shared repositories, so treat them as optional at every call site.
Also catches up on API surface already merged upstream: line growth
request/response models, forecast mechanics, and plan-history backfill.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Regenerates the SDK against the backend
refactor/analytics-to-usagebranch, picking up the graph endpoint rename and the new instance-resource fields on the health response.Important
Merge after the backend PR. These routes do not exist on
mainyet — merging this first would ship a client pointing at 404s.Changes
Endpoint rename (backend P0)
/v1/graphs/{graph_id}/analytics/v1/graphs/{graph_id}/metrics/v1/graphs/{graph_id}/analytics/usage/v1/graphs/{graph_id}/usageget_graph_metricskeeps its name — only its URL moved, so callers are unaffected.get_graph_usage_analytics→get_graph_usage(git records it as a 98% rename). It had no consumers.Instance resources on
DatabaseHealthResponsecpu_usage_percent,memory_usage_percent,resource_status(idle/busy/constrained).memory_usage_mbis now actually populated — it had been declared and hardcodedNoneserver-side.nullon shared repositories, so treat them as optional at every call site.Upstream catch-up (already merged server-side, not part of this initiative)
LineGrowthLite,LineGrowthLiteValuesByPeriod,LineGrowthRequest,LineGrowthRequestValuesByPeriodType0ForecastMechanics,CreateForecastRequest,UpdateForecastRequest,BackfillPlanHistoryOperationTesting
just test-all— ruff check, ruff format, basedpyright 0 errors, 439 passed / 17 skipped: all green.Pure regen output — no hand edits. Version bump / release handled separately by the publish flow.