When does the merge process fail?

The merging process requires a conflict check between the currently active configuration and the changed configuration. Airlock Gateway checks which parts of the two configurations have been altered. For example: In case the same domains have been altered in both configurations, merging will not be possible.

• Merging is not possible when both configurations show concurrent modifications of:
• virtual hosts,
• mappings,
• back-end groups,
• server certificates,
• a global setting.

• However, merging is possible when changes between both configurations are made as follows:
• Virtual hosts can be merged with modifications of other virtual hosts or objects of other types.
• Mappings can be merged with modifications of other mappings or objects of other types.
• Back-end groups can be merged with modifications of other back-end groups or objects of other types.
• Changes of a server certificate can be merged with modifications or changes of other server certificates or objects of other types.
• Global settings can be merged with a modified virtual host, mapping, back-end group and server certificate only.

• Changing a connection between virtual host–mapping or mapping–back-end group will alter both connection endpoints and can unintentionally prevent merging.
• Changes on Custom Deny Rules affect all mappings and can therefore prevent merging.
• Modification of error pages or certificate revocation lists (CRLs) will prevent merging when pages or lists have been changed in both configurations.
• Via Configuration Center only:
  A special feature copies shared patterns (e.g. in allow rules, deny rule exceptions etc.) into multiple mappings if applicable. Changing a shared pattern thus can change multiple mappings and can unintentionally prevent merging.
  The Gateway REST API currently does not support shared patterns.