...
https://apiida.atlassian.net/wiki/spaces/AAGM/pages/1520009389/Migrations#Mappings
...
Services and Policies & Environmental Configuration
In the first column of the tables you will see the respective name of the resource for this mapping and, secondly, the type. By clicking on the eye symbol, you can view the source code of the resource and also detect the differences.
“Prediction" tells you what will happen to this resource on the target.
In "Mapping" you can see how the mapping of the source resource and the target resource came about. You can also adjust this manually here by clicking on "...".
The selected behavior for this mapping can be adjusted in "Action". For example, "Ignore" can be used to exclude a resource from the migration. A connection to the database should be set to "NewOrExisting".
The standard action can be adjusted globally in the configuration. The "Manage Default Mappings" button at the bottom takes you directly there.
The mappings can be linked using the checkbox in front of each action selection box and all of them can be changed at once using the selection box above, to the right of the search.
If you have several targets for this migration, you can also include all targets in this link by activating "Link Actions across Targets" above the selection box
can be used to save a mapping action individually for this resource.
With these tools, you can configure your migration very efficiently.
...
Requirements
APIs and libraries can have requiremets and these are listed in the bottom container. Even before the migration, we check whether the requisitions are available on the target!
...
If the requirement needs to be updated or is not displayed at all, you will also receive a large warning message.
Pipeline
In "Pipeline" you can perform various actions before and after the migration, such as "Disable via Admintools" or "Call an URL via GET". Default values can be set in Environments.
...