Repository navigation
feat(migrations)!: pivot to declarative .m4d and CLI-first workflows - #4
Merged
Merged
Conversation
Replace imperative migration scripts with .m4d definitions and lifecycle hooks, and make the self-contained CLI the recommended entry point. Update examples, documentation, release notes, packaging, and dashboard startup to match the new workflow. Also normalize Dataverse target rows before upstream writes. Co-authored-by: Copilot <[email protected]>
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.
What changed
.ps1migration jobs with executable.m4ddefinitions using a root$Migrationobject,Steps,Connections,RunOptions, and optionalPreRun/PostRunhooks.m4d run <file>the recommended entry point. Keep advanced PowerShell usage throughInvoke-M4dMigration -Path, move the scheduler toInvoke-M4dMigrationGraph, and addNew-M4dMigrationFile/m4d new-filefor a commented starter template.--no-dashboardfor headless runs; low-level CLI commands are grouped underadvanced.Countas entity columns.Why
This is a major pivot toward a flexible, fast, easy-to-install engine optimized for Dataverse and the age of AI coding agents. Declarative
.m4dfiles make migration jobs inspectable and easier to author, while the self-contained CLI removes setup friction for the default workflow.Validation
dotnet build Migration4Dataverse.slnx --configuration Release --no-restore— passed with 0 warnings and 0 errors.dotnet test Migration4Dataverse.slnx --configuration Release --no-build— 360 passed.build/Test-MigrationModulePackage.ps1 -Version 0.1.0with an isolated output directory — passed.git diff --check— passed.The sequential Dataverse example was resumed against an isolated SQLite database with the dashboard enabled. The live run had not yet completed when this PR was opened, so it is not counted as a completed end-to-end validation.