Field history tracking resolution DR

[gnemiq]

Checklist

All items have to be completed before a PR is merged

• [x] Adhere to Contribution Guidelines
• [ ] Updates to Decision Records considered?
• [ ] Updates to documentation at DX@Scale Guide considered?
• [ ] Tested changes?
• [ ] Unit Tests new and existing passing locally?

[codecov-commenter]

Codecov Report

Base: 51.85% // Head: 51.85% // No change to project coverage :thumbsup:

Coverage data is based on head (863dd36) compared to base (353797f). Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1134   +/-   ##
=======================================
  Coverage   51.85%   51.85%           
=======================================
  Files          74       74           
  Lines        3321     3321           
  Branches      710      710           
=======================================
  Hits         1722     1722           
  Misses       1599     1599           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

[rody]

Adding here the summary of the discussion with @azlam-abdulsalam on Slack:

The discussion was about not introducing another file format to maintain but use the metadata files to manage the history tracking. This to ensure that we don't add another "way of working" from a dev perspective.

1. use the "normal" metadata (i.e. CustomField metadata) as the source of truth (no changes from a dev perspective)
2. exclude the standard and prefixed metadata (i.e. metadata that we don't own) from the package/deployment
3. from all the metadata (owned and not-owned) generate an input (CSV,JSON,....) for the "alignment" script.
4. after package installation/deployement run the script on-platform to update only the fields that are ignored during installation (ex. the tracking history) and the modifiable fields on non-owned metadata (with the input from 3).

This will prevent the dev from having another file to maintain. They can still use the normal flow (update on SO, retrieve, commit).