Engineer uses migrations to track configuration changes made to SharePoint. You can use migrations to create a queue of tasks that are executed in order on any number of target environments. Think of migrations as source control for your configuration operations.
make command to create new migration files. Once created, you can use Engineer’s migration API to create fields, content types, lists, views, and more.
Using the Migration API
down method. Tasks defined in the
up method will be executed during
migrate operations. Tasks defined in the
down method will be executed during
rollback operations. This allows you to define a queue of tasks that are executed during both deployment and retraction of each migration.
Each of these methods passes a single parameter called
engineer through to your migration logic. You can use this
engineer object to access the migration API.
The same API is accessed in both the
down methods. There are a variety of API endpoints, options, and configurations you can use to do just about anything within your SharePoint environments. Refer to the individual API documentation for more information on how to use each endpoint.
To learn more, we recommend starting with the
Web documentation, as all Engineer tasks must begin with a
The Migration Queue