Clarification regarding is_backup field in PkgAcct::Create event

[sangeeths]

Our integration is hooking into PkgAcct::Create and PkgAcct::Restore events to aid in user transfer from one server to another for reactivation. We noticed that the hook gets invoked many times with is_backup=0 and is_backup=1. Based on our observations, is_backup=0 is what our integration needs to use to detect the transfer of account event. However, we weren't sure based on reading the API docs that is_backup=0 indicates the "account transfer" use case.

Account transfers currently user pkgacct script as follows:

$cpscripts/pkgacct --skiphomedir username /root/cpanel_backups/

and subsequently the cpmove archive is copied over to the new server and restored with:

$cpscripts/restorepkg --allow_reseller cpmove-username.tar.gz

For this and similar use cases, would is_backup=0 be the case all the time? And is is_backup=1 set if --userbackup or --backup=FILEPATH as described over here: The pkgacct Script | cPanel & WHM Documentation

Would greatly appreciate clarifications on when 1 or 0 will be set for this field.

 

[cPRex]

Hey there! I'm looking into this and I'll let you know once I have an update.

 

[cPRex]

I just wanted to let you know our team is still looking into this and I'll post an update once I get more details.

 

[cPRex]

I did some testing with the backup team and you are correct - the =0 value is the one that will normally be used. =1 would be used if either backup or userbackup is true/has a value.

 

[sangeeths]

I did some testing with the backup team and you are correct - the =0 value is the one that will normally be used. =1 would be used if either backup or userbackup is true/has a value.

Thanks a lot! Greatly appreciate the quick responses on the questions asked over here from you and the rest of the team

 

[cPRex]

You're very welcome!