Updating a SaaS application
Updating the configuration of a SaaS application may include:
- Changing the parameters of tariff plans and options.
- Adding tariff plans and options.
- Deleting tariff plans and options.
To update a SaaS application in the marketplace:
-
Edit the service configuration file.
-
To keep the currently published revision of the service available in the test namespaces of the marketplace, insert a new section describing the new service configuration into the JSON file:
null{"services": [{<SERVICE_PARAMETERS>,"preview": {"parameters": []},"plans": []},{<SERVICE_PARAMETERS>,"preview": {"parameters": []},"plans": []}]}If the current revision of the service does not need to remain available in the test namespace of the marketplace, skip this step.
-
Describe the new service configuration (for more details, see the section SaaS application configuration).
-
In the new service configuration, specify a new revision of the service.
-
If the parameters of tariff plans have been changed, specify new plan revisions in the new service configuration.
-
-
If tariff plans have been added or deleted, edit the
resources/plan_mapping.jsonfile in the broker directory (for more details, see the section Uploading service configuration to the broker). -
The marketplace periodically requests the current service configuration from the broker, so the new configuration will automatically appear in the test namespace of the marketplace.
-
Test the new service revision in the test namespace of the marketplace (for more details, see the section Service testing in the marketplace).
-
Publish the new service revision in the public namespace of the marketplace (for more details, see the section Service publication).
The previously published revision moves to the test namespace of the marketplace if it is preserved in the service configuration file. All unpublished revisions described in the service configuration are preserved in the test namespaces.
Service revisions removed from the service configuration will not be available in either the test or public namespaces of the marketplace.
Publishing a new revision does not affect the already existing service instances (tenants/accounts). The revision of these service instances does not change, even if it has been removed from the service configuration and is unavailable in the marketplace.