Skip to content

[gen2-migration] Pre-flight validation should name the specific table(s) failing the DeletionProtectionEnabled check #14980

Description

@sarayev

Summary

Import validation checks DeletionProtectionEnabled on source tables, but when one table fails, the result is an opaque whole-data-stack failure with no indication of which table is non-compliant.

Expected

A pre-flight validation step that names the specific table(s) failing the DeletionProtectionEnabled check, before any deploy is attempted — independent of the enable/disable logic itself.

Type

Enhancement (usability / diagnostics)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions