testserver: echo postgres spec on GET to match backend; recapture goldens - #5976
Merged
Conversation
…dens The Lakebase (postgres) backend now echoes the submitted spec on GET; before it returned only status. This broke the nightly cloud run: direct-engine plans for postgres resources started showing spec fields in remote_state and dropping the phantom spec:input_only skip-changes. The *Remote structs already anticipate this, so only the fake server and goldens were stale. Verified on a real workspace: a created project's GET returns spec with the fields the user set. Recaptured goldens against a real cloud workspace and the full postgres acceptance suite passes locally and on cloud. Co-authored-by: Isaac
janniklasrose
approved these changes
Jul 20, 2026
pietern
enabled auto-merge
July 20, 2026 09:58
Collaborator
Integration test reportCommit: 3635dae
8 interesting tests: 4 RECOVERED, 4 SKIP
Top 10 slowest tests (at least 2 minutes):
|
Collaborator
Integration test reportCommit: b6538fe
18 interesting tests: 8 FAIL, 4 RECOVERED, 3 flaky, 2 SKIP, 1 KNOWN
Top 50 slowest tests (at least 2 minutes):
|
pranavdev022
pushed a commit
to pranavdev022/cli
that referenced
this pull request
Jul 31, 2026
## Changes - Effectively revert databricks#5976 - Update tests ## Why `spec` is no longer being echo'ed ## Tests Ran against cloud
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
3 participants
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.
Why
The Lakebase (postgres) backend now echoes the submitted
specon GET; before it returned onlystatus. This broke the nightly cloud run: direct-engine plans for postgres resources started showing spec fields inremote_stateand dropping the phantomspec:input_onlyskip-changes. The*Remotestructs already anticipate this, so only the fake server and goldens were stale.Verified on a real workspace: a created project's GET returns
specwith the fields the user set. Recaptured goldens against a real cloud workspace and the full postgres acceptance suite passes locally and on cloud.Notes
No
resources.ymlchange needed: thespec:input_onlyannotations are now redundant but benign (they only suppress phantom drift when config is unchanged) and self-heal once the OpenAPI schema dropsINPUT_ONLY.This pull request and its description were written by Isaac.