Skip to content

Chore #125: Rename import/happy fixture and regenerate output - #129

Merged
micheledaddetta-databricks merged 1 commit into
mainfrom
chore/125-rename-import-fixture-and-regen
Apr 29, 2026
Merged

Chore #125: Rename import/happy fixture and regenerate output#129
micheledaddetta-databricks merged 1 commit into
mainfrom
chore/125-rename-import-fixture-and-regen

Conversation

@micheledaddetta-databricks

Copy link
Copy Markdown
Owner

Closes#125

Summary

Why

PR #126 (E.0) removed the stub guard whose error message PR #123 had locked into this fixture. As a result the acceptance suite has been failing on main since #126 merged, blocking E.1 (#128) and any future PR's acceptance gate. The directory was also misleadingly named (happy/ for an error-path fixture); the rename in #125 was deferred work that's cheaper to fold into this fix-up than to keep two issues open. pending_95 (the name #125 originally proposed) no longer fits either since the new failure isn't about the #95 stub - it's a clean 404 from the workspace API.

Test plan

  • GOPROXY=direct GOTOOLCHAIN=local GOSUMDB=off go test ./acceptance -run 'TestAccept/ucm/import' -count=1 -> green
  • GOPROXY=direct GOTOOLCHAIN=local GOSUMDB=off go test ./acceptance -run 'TestAccept/ucm' -count=1 -> green (full UCM acceptance suite)
  • Both DATABRICKS_BUNDLE_ENGINE=terraform and DATABRICKS_BUNDLE_ENGINE=direct variants share the same output.txt.

Fork-divergence notes

  • Edits to upstream files: none.
  • New touchpoints outside cmd/ucm/**, ucm/**, .claude/**, .github/workflows/upstream-sync.yml: only acceptance/ucm/import/** (rename + regenerated output). This is fork-only test scaffolding, no upstream conflict surface.

Base branch

main. Not stacked.

Notes for reviewer

The new locked-in behavior is a clean error from inside the import flow (404 from the workspace API surfaced via direct import: ...), not a panic or opaque crash - so this fixture remains a useful regression guard. When E.1+ lands a real reachable happy path, we can add import/happy/ back as a separate fixture and decide whether to retain missing_catalog/ as a 404-error guard.

PR #126 (E.0) removed the ProcessUcm-level "direct engine is not yet
supported" stub, which silently invalidated this fixture: the assertion
PR #123 locked in (the stub error message) is no longer reachable.
Rename `acceptance/ucm/import/happy/` -> `acceptance/ucm/import/missing_catalog/`
and regenerate `output.txt`. The directory name now describes what is
actually being asserted: importing a non-existent catalog produces a
structured 404 from the workspace API. The old `happy` name was
misleading (no happy path exists yet), and `pending_95` (the rename
proposed in #125) is also obsolete now that the stub is gone.
The new output is identical across both DATABRICKS_BUNDLE_ENGINE matrix
variants, so a single output.txt covers both.
Closes#125.
Co-authored-by: Isaac
@micheledaddetta-databricksmicheledaddetta-databricks added ucm ucm subcommand work area/smoke smoke/acceptance fixtures chore non-functional maintenance labels Apr 29, 2026
@micheledaddetta-databricks
micheledaddetta-databricks merged commit 0bb9913 into mainApr 29, 2026
11 of 14 checks passed
@micheledaddetta-databricks
micheledaddetta-databricks deleted the chore/125-rename-import-fixture-and-regen branch April 29, 2026 12:47
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/smokesmoke/acceptance fixtureschorenon-functional maintenanceucmucm subcommand work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ucm: Rename acceptance/ucm/import/happy → import/pending_95 (locks in error path, not happy path)

1 participant

@micheledaddetta-databricks