In order not to set the same mappings over and over again in each migration, you can also define standard mappings in the migration overview. These are set automatically when a new migration is created.
...
.
How are the actions of the mapping set?
The first/weakest definition is the bottom “Default Actions by Type”,
all set actions would then be overwritten by what's in “Default Actions by Type and Regex” defined
and these set actions would then be overwritten by what's in “Stored Manual Migration Mappings” defined.
...
Stored Manual Migration Mappings (Action and Target)
Here you can view the mappings you have customised customized and saved. In each new migration, the corresponding action is set for the elements in the table.
This is the most precise definition and always wins.
https://apiida.atlassian.net/wiki/spaces/AAGM/pages/5060100152/Perform+a+Migration#Mappings
...
Default Actions by Type and Regex
Several regular expressions can be defined for each type. The last/lowest expression for the respective type wins. When preparing a migration, these expressions are applied one after the other against the name of each element of a migration for each target.
For example, the regular expression /^[a-zA-Z0-9]+$/ can be used to set all actions for the selected type to Ignore.
Default Actions by Type
Here you can see and define the standard actions for each type of resource of a Layer7 gateway.
The more specific definitions above overwrite these.