You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing parallel builds and comparing output of mixer in a dev environment to a prod environment, all of the manifests in the Manifest.MoM have different hashes. This is because of the timestamp field in the manifest header.
Is this something we can remove so that debug work is made easier? If I'm not mistaken, when a manifest is signed, that signature has its own timestamp, so maybe we can overlook this value?
The text was updated successfully, but these errors were encountered:
reaganlo
changed the title
Question: Should we remove the timestamp field in the manifest header?
Should we remove the timestamp field in the manifest header?
Dec 16, 2019
When doing parallel builds and comparing output of mixer in a dev environment to a prod environment, all of the manifests in the Manifest.MoM have different hashes. This is because of the timestamp field in the manifest header.
Is this something we can remove so that debug work is made easier? If I'm not mistaken, when a manifest is signed, that signature has its own timestamp, so maybe we can overlook this value?
The text was updated successfully, but these errors were encountered: