Details
New Feature
Major
Description
Consider this:
Extra IPs are ordered at checkout, the client wants to cancel one. They must be able to see a list of their IPs, and cancel the specific ones they no longer need.
This is tricky because additional IPs are often billed. So, if there was a way in a module view for a client to delete an IP (effectively returning it to the pool in SolusVM), it must necessarily also affect the count of extra IPs that they have and are billed for.
This needs some further discussion.
Issue Links
Activity
The way this would have to work is as follows:
- The module would define a management tab that would then invoke Services::edit(), passing in the updated $vars, which contains the modified quantity value on the appropriate config option, as well as a new field that defines the IP addresses to be removed.
- All service config options need to be passed through or they will be removed.
- Services::edit() would invoke the module's editService() method. This would look for the IP addresses to be removed, and make the API request to do so.
- Services::edit() will handle the rest, but updating the service record and config options accordingly.
Cody Phillips (Inactive)
added a comment - The way this would have to work is as follows:
The module would define a management tab that would then invoke Services::edit(), passing in the updated $vars, which contains the modified quantity value on the appropriate config option, as well as a new field that defines the IP addresses to be removed.
All service config options need to be passed through or they will be removed.
Services::edit() would invoke the module's editService() method. This would look for the IP addresses to be removed, and make the API request to do so.
Services::edit() will handle the rest, but updating the service record and config options accordingly.
A module can not change the quantity of a configurable option.
The only thing a module has control over is the service meta field data.