u/DeepFryEverything

We've used DAB-commands like Validate and Plan for a while - to print Github PR-comments on what the PR will change, delete and create. But we are struggling to catch breaking changes before they are committed to main.

Some examples:

After migrating a pipeline to serverless compute, our branch passed the plan in the PR stage, but failed in main due to You must use the Advanced edition when using serverless compute. (400 INVALID_PARAMETER_VALUE) which is something I would expect CI to catch.

Another example is Lakeflow generating a new pipeline-ID, which means during deploy it will try to apply itself to an existing pipeline and fail on mismatching pipeline-ids. Again, would've loved to fail in CI instead of main.

How are you solving this?