when manta gets the details of a CFS configuration, if fetches the ref details. If the ref is an annotated tag, then it will show the tag SHA which is different than the commit SHA it points to. This is default git behavior since annotated tags are an object themselves. However the manta get configuration output is confusing because the tag SHA is different than the commit id.
Operational side this should not have major implications since CFS session do a git checkout <SHA> to switch branches and if <SHA> is an annotated tag, then git will resolve it to the commit it points to automatically.
Probably.
when manta gets the details of a CFS configuration, if fetches the ref details. If the ref is an annotated tag, then it will show the tag SHA which is different than the commit SHA it points to. This is default git behavior since annotated tags are an object themselves. However the manta get configuration output is confusing because the tag SHA is different than the commit id. Operational side this should not have major implications since CFS session do a
git checkout <SHA>
to switch branches and if<SHA>
is an annotated tag, then git will resolve it to the commit it points to automatically. Probably.