Added artisan user:restore and domain:restore commands
|271 ↗||(On Diff #5308)|
Isn't STATUS_LDAP_READY removed when the associated job is done?
|20 ↗||(On Diff #5308)|
Marking a domain as deleted in LDAP is still valid, though, so I'd expect the domain to show up in LDAP with inetdomainstatus &= 8.
When a domain is restored, we don't update the updated_at column of the entitlements table because it's used to track payment status / due dates for new charges.
I believe created_at will remain what it was, which would be the expected result.
I also believe $domain->save() will automatically update updated_at.
Here too, please avoid touching updated_at.
|733 ↗||(On Diff #5308)|
This should be an effect of having the associated jobs executed successfully, no?
I don't understand this part.
When firstname.lastname@example.org deletes itself and needs to be restored, is the situation not always that both the User as well as the Domain are deleted?
Does it then mandate that first user:restore email@example.com is ran?
It's just that you cannot restore a domain before restoring the user. But the command is still useful if you restore a domain (one of many) on an existing account.