All Collections
Problem analyzers
Different "label" tags
Different "label" tags
Gabriel Cowley avatar
Written by Gabriel Cowley
Updated over a week ago

This problem analyzer fixes a naming mismatch issue with components that can cause deployments to fail.

What triggers this problem analyzer?

When there is a component that exists in both the source and target of a comparison, but whose label tag is different, this problem analyzer will be triggered.

What problem is it solving?

The value of the label tag denotes the name of the site represented by the component. If the name of the site is later changed, the naming convention used for the label values on each side of the comparison becomes mismatched. This will cause a deployment to fail.

How does it work?

Gearset will provide the option to temporarily replace the value of the label tag in the source-side component with that of the target-side component, in order to facilitate the validation or deployment of the changes.

Did this answer your question?