Conflicts

Whenever multiple applications share an asset in their deployment stacks, conflicts may arise due to different migration strategies. A conflict in the migration of assets that are shared by multiple applications can be caused by

• opting for different migration strategies for the applications between which assets are shared.

• choosing the same migration strategy for the applications, but moving to different cloud providers.

• choosing the same strategy and provider, but different locations for the applications.

Txture features an overview that lists all conflicting asset migration actions. In the general view of the target architecture in the transformation cockpit you can find the Conflicts card along with the Show conflicts option in the center top.

The overview will show you the information required to resolve the issues. It lists all applications which use the asset and each of the chosen migration actions that are in conflict. For example, the screenshot above shows a physical server that is set to be both retained and replaced by a virtual machine for two different applications that share the server. You can also view conflicts in the context of a single application by selecting an application from the left sidebar. The application-specific view of the conflicts will only show issues regarding assets that are part of the selected application's deployment.

In order to resolve a conflict you can click on "Resolve Conflict" to create a Shared Component. Once you have aligned all migration actions for an asset it will be removed from the list of conflicts and can be re-shown by selecting the "Show resolved conflicts" toggle switch.