Add support for deploying a name change to a SFDC component (such as profile)
We occasionally change profile names during permssions clean-up projects. Currently, when you deploy a profile with a changed name, Gearset recognizes it as a "new" and a "deleted" profile, instead of a single "changed" component, which makes the deployment challenging.
I know that the name is used as an identifier, since the Id may not always match between source and target. However, if you add support for this, the tool could try to identify components with name changes by looking for the same Id in source and target with a changed name.
Kevin Hong commented
We have run into the same issue and have found a workaround to address this, not ideal. From a tooling perspective, this seems like a big challenge especially if you want to persist the name change to git source control (i.e. you don't have a metadata ID to compare in this case, only the file name which has now changed. Trying to do any sort of hash or some deterministic approach is also tricky if aside from the rename the profile was also updated. I think if salesforce includes some sort of unique identifier in the metadata xml, it could be possible and gearset take the appropriate action to rename the file then perform a checkout, update, commit, something to that effect. Would love to see how this problem can be tackled by the gearset team.