-
Notifications
You must be signed in to change notification settings - Fork 4.1k
sql: register http routes after version initialization #138342
Copy link
Copy link
Closed
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-observabilitybackport-24.3.xFlags PRs that need to be backported to 24.3Flags PRs that need to be backported to 24.3branch-release-24.2Used to mark GA and release blockers, technical advisories, and bugs for 24.2Used to mark GA and release blockers, technical advisories, and bugs for 24.2branch-release-24.3Used to mark GA and release blockers, technical advisories, and bugs for 24.3Used to mark GA and release blockers, technical advisories, and bugs for 24.3v24.2.10v24.3.5
Description
#127170 made it so that the version is set just after the http routes are registered. Using the http routes before versio initialization leads to fatal errors. We should ensure that the routes are only available after the version is initialized.
Jira issue: CRDB-46051
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-observabilitybackport-24.3.xFlags PRs that need to be backported to 24.3Flags PRs that need to be backported to 24.3branch-release-24.2Used to mark GA and release blockers, technical advisories, and bugs for 24.2Used to mark GA and release blockers, technical advisories, and bugs for 24.2branch-release-24.3Used to mark GA and release blockers, technical advisories, and bugs for 24.3Used to mark GA and release blockers, technical advisories, and bugs for 24.3v24.2.10v24.3.5