|
|
|
|
Configuration script declared for particular service may be able to change this service status. This configuration script ability is declared with the status-control element in the package metadata file. For details, refer to the 5.3.2.1.5 Enabling/Disabling Service section in the Specification.
When the Controller determines that the service status may be changed, the use and storage of this information completely depends on the Controller implementation. For example, it may provide to end-user some control for either service disabling or service enabling or both operations. The other use case, the Controller changes service status basing on end-user account balance: disables service, if user is lack of funds and enables it, when its balance is replenished.
The Specification provides the only requirement to disabled service that it is must not serve to its users or operate on behalf of service owner. If the service uses some hosting resources, whether to leave them allocated or to free, depends on the Controller implementation.
The procedure of changing service status just slightly differs from other configuration script invocations. Depending on service current status, the Controller invokes configuration script with the enable or disable argument. The Controller must pass to the configuration script all service information transformed into respective environment variables: settings (SETTINGS_<id>), except marked as installation-only; application URL mapping environment variables (if any), as defined by the Specification in section 5.3.2.2. Environment Variables.
For details on configuration script invocations, refer to the Configuration Script section.
