Submitted by Hal9000 on Sat, 02/08/2014 - 10:27
There is a problem with the --apply-plan parameter in my opinion. That is, I had some clients which for example disabled the mail service since they use their own external server. So when they want to upgrade to a new plan to have more databases or more web space for instance, I want to apply the new plan. But this causes the mail service to reactivate, which also adds MX records to the DNS zone. And this is very bad because they will lose emails. So I think what --apply-plan should do is apply all the limits, and as far as features goes, only apply the new features the old plan did not have. Or maybe just add an --apply-plan-limits parameter or something like that.
Status:
Closed (works as designed)
Comments
Submitted by JamieCameron on Sat, 02/08/2014 - 12:08 Comment #1
I had a look at the modify-domain API call, and it doesn't apply features from the plan at all even with the --apply-plan flag. It may grant the permissions to use features, but doesn't actually activate them.
Submitted by Hal9000 on Sat, 02/08/2014 - 12:10 Comment #2
Weird. Ok I will do some more testing. Just ignore this for now :)
Submitted by JamieCameron on Sat, 02/08/2014 - 12:22 Comment #3
Submitted by Hal9000 on Sun, 02/09/2014 - 04:38 Comment #4
I apparently found the cause of the problem. I am writing it here for reference. Basically I also sent a plan-features="" parameter to the command. Removing that parameter altogether left the features alone.