engineer make <name>
Create a new migration file.
- A descriptive name for the new migration (required)
make command is used to create a new migration file template. This template will be placed into a
migrations directory under the current working directory (a new directory will be created if it does not exist). Each migration file is timestamped with the current UTC time. This ensures that migrations can always be run in order, or rolled back in reverse order.
Organization and Naming
The organization and naming of your migrations is entirely up to you. We recommend that you organize migrations into concise files that focus on a single operation. Avoid huge migration files that perform many actions. This will allow more granular control over migration operations in the future.
As an example, a solution that deploys a content type may have several migrations, such as:
By organizing your migrations in such a way, you and other developers on your team will be able to easily roll back and migrate specific features of your configuration solution at any given time.
Important Note on Persistent Naming
Engineer uses each migration’s file name to track migration status in SharePoint environments. Do not change migration file names once they have been migrated to any environment, else Engineer will see the file as an entirely new migration.