API call for createacct should use defaults set in Tweak Settings
Needs Feedback
As a systems administrator who occasionally needs to automate things using the API, I would like API calls to respect defaults set in Tweak Settings.
In particular, I would like the createacct API call to respect the defaults for SPF and DKIM records.
Thanks!
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
This seems like it could be argued for and against pretty easily. The argument against this being that createacct would then have different behavior for the same API call made on different cPanel & WHM servers. Consistency where "this API call will do the same thing on any server" seems like a favorable behavior. This is primarily a point I raise because we'd then be changing behavior of an API call from an established history. I could see various WHMCS and other similar deployments "suddenly" deploying accounts differently and the frustration from that.
Is this a concern anyone else has, or is it more important to unify the createacct behavior with the behavior experienced through the UI?A compromise would be to add an argument or some method of instructing the createacct call to utilize the server-specific defaults versus the API defaults, thereby allowing this new behavior without retroactively changing prior behavior.
I'd like more discussion/feedback on this to see where the stances reside on this.
This seems like it could be argued for and against pretty easily. The argument against this being that createacct would then have different behavior for the same API call made on different cPanel & WHM servers. Consistency where "this API call will do the same thing on any server" seems like a favorable behavior. This is primarily a point I raise because we'd then be changing behavior of an API call from an established history. I could see various WHMCS and other similar deployments "suddenly" deploying accounts differently and the frustration from that.
Is this a concern anyone else has, or is it more important to unify the createacct behavior with the behavior experienced through the UI?A compromise would be to add an argument or some method of instructing the createacct call to utilize the server-specific defaults versus the API defaults, thereby allowing this new behavior without retroactively changing prior behavior.
I'd like more discussion/feedback on this to see where the stances reside on this.
This seems like it could be argued for and against pretty easily. The argument against this being that createacct would then have different behavior for the same API call made on different cPanel & WHM servers. Consistency where "this API call will do the same thing on any server" seems like a favorable behavior. This is primarily a point I raise because we'd then be changing behavior of an API call from an established history. I could see various WHMCS and other similar deployments "suddenly" deploying accounts differently and the frustration from that.
Is this a concern anyone else has, or is it more important to unify the createacct behavior with the behavior experienced through the UI?A compromise would be to add an argument or some method of instructing the createacct call to utilize the server-specific defaults versus the API defaults, thereby allowing this new behavior without retroactively changing prior behavior.
I'd like more discussion/feedback on this to see where the stances reside on this.
This seems like it could be argued for and against pretty easily. The argument against this being that createacct would then have different behavior for the same API call made on different cPanel & WHM servers. Consistency where "this API call will do the same thing on any server" seems like a favorable behavior. This is primarily a point I raise because we'd then be changing behavior of an API call from an established history. I could see various WHMCS and other similar deployments "suddenly" deploying accounts differently and the frustration from that.
Is this a concern anyone else has, or is it more important to unify the createacct behavior with the behavior experienced through the UI?A compromise would be to add an argument or some method of instructing the createacct call to utilize the server-specific defaults versus the API defaults, thereby allowing this new behavior without retroactively changing prior behavior.
I'd like more discussion/feedback on this to see where the stances reside on this.
For us, keeping the API consistency makes sense and adding an optional argument to use server specific defaults. If the argument isn't used, then the API defaults are used.
For us, keeping the API consistency makes sense and adding an optional argument to use server specific defaults. If the argument isn't used, then the API defaults are used.
Replies have been locked on this page!