Repository navigation
test(databricks): add protected live release deployment smoke - #241
Merged
Merged
Conversation
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
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.
Tracks DaorynAI/semapact-project#127.
Summary
semapact_smoke_*schemas and unique generated table names;The smoke uses the canonical application workflow and normal Databricks unified-auth boundary. It does not introduce a second deployment path.
Completion rule
Merging this PR installs the smoke framework only. Private roadmap issue #127 remains open until the workflow is executed successfully against a real Databricks workspace and the live CREATE / ADD COLUMN / release provenance / repeated NO_OP assertions all pass.