Conflict resolution

This topic tells you how to resolve conflicts that Application Accelerator transforms in Tanzu Application Platform (commonly known as TAP) might produce.

For example, if you’re using Merge or RewritePath, a transform can produce several files at the same path. The engine then must take an action: Should it keep the last file? Report an error? Concatenate the files together?

Syntax reference

Conflicts can arise for a number of reasons. You can avoid or resolve them by configuring transforms with a conflict resolution. For example:

• You can explicitly end a transform Chain with a UniquePath, which by default uses Fail. This is customizable.

Chain

engine {
  T1()
  T2()
  UniquePath(CONFLICT-RESOLUTION)
}

Where CONFLICT-RESOLUTION is the resolution strategy you want to use from the list in Available strategies.

Available strategies

The following values and behaviors are available:

• Fail: Stop processing on the first file that exhibits path conflicts.
• UseFirst: For each conflicting file, the file produced first (typically by a transform appearing earlier in the YAML definition) is retained.
• UseLast: For each conflicting file, the file produced last (typically by a transform appearing later in the YAML definition) is retained.
• Append: The conflicting versions of files are concatenated (as if using cat file1 file2 ...), with files produced first appearing first.
• FavorOwn: Only makes sense in the context of composition. Selects the version of the file that comes from the current executing fragment if possible, falls back to the caller version otherwise.
• FavorForeign: Only makes sense in the context of composition. Selects the version of the file that was provided by the caller if present, falls back to the file originating from this fragment’s fileset otherwise.
• NWayDiff: Try to merge the conflicting resources by applying patches computed against a common ancestor. The resulting resource has the attributes of the first conflicting resource.

See also

• UniquePath