Package deployment backout?
We've been looking for 5 years (see PDN question)
[this is posted elsewhere in Mesh, but I can't access it anymore..]
When Pega does a package install (or deployment, migration), it does 2 things:
- Inserts new rule/data records
- Updates existing rule/data records
Following best practice, the insert is of a new version, and not replacements to an existing version.
If necessary, this can be reverted by ruleset-limiting in the application.
How to revert the updates?
The update stores the previous records in History-Data-xxx... couldn't there be a way to programmatically restore the version prior to the install time?
If it did that, a deployment undo could be fairly trivial, and not require a database restore.
Pegasystems
US
>>> When Pega does a package install (or deployment, migration), it does 2 things: 1) Inserts new rule/data records 2) Updates existing rule/data records
One more thing I can think of that is done by the zip import screen is defining schema. For instance, if you create new class groups and migrate them, you can see this happening.
However, regarding your idea about using history records for restoration, I believe that kind of restoration is already available on a limited basis. For instance, if you delete a rule using the available UI on the ruleform, even if you delete the tab, you can go back to the "recents" list on the left margin of the developer portal to restore the rule. (wasn't there a way to restore rules even on older prpc versions even before that "recents" list existed on developer portal ?) /Eric
BNY Mellon
US
Correct -- I omitted schema changes, possibly because we manage schema changes outside of Pega here.
Yes, the restoration is available manually, one instance at a time. What we're advocating is for a way to automate this.