Skip to content
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.

Migrate sfpowerscripts artifact record to use custom settings #476

Closed
azlam-abdulsalam opened this issue Apr 6, 2021 · 0 comments · Fixed by #477, #545 or #548
Closed

Migrate sfpowerscripts artifact record to use custom settings #476

azlam-abdulsalam opened this issue Apr 6, 2021 · 0 comments · Fixed by #477, #545 or #548
Assignees
Labels
enhancement enhancement to existing feature

Comments

@azlam-abdulsalam
Copy link
Contributor

sfpowerscripts artifacts is an unlocked package that keeps track of all the packages installed in the org. The current implementation utilizes a custom object to store the information. However, this has a downside, that when an org gets refreshed, the entire data gets wiped out and the traceability is lost.

To solve this, these records should be stored in custom settings, which are preserved during refreshes. The cli should support utilising custom settings to store these records with a backward compatibility layer, so that none of the data gets lost while the migration is underway

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.