We were presuming that any manifest name other then 'default.xml' was one of our integration manifests, thus activating the 'use-head-next' override. What was also happening was that some clients that created a top level manifest to also sync their own layers, or even Common Torizon (which uses common.xml) were wrongly interpreted as integration manifests.
Now we explicitly check for 'integration.xml' and 'next.xml' as they're our integration layers.
We were presuming that any manifest name other then 'default.xml' was one of our integration manifests, thus activating the 'use-head-next' override. What was also happening was that some clients that created a top level manifest to also sync their own layers, or even Common Torizon (which uses common.xml) were wrongly interpreted as integration manifests.
Now we explicitly check for 'integration.xml' and 'next.xml' as they're our integration layers.
Closes #86