Updating a SaaS applicationBeta
A SaaS application must be updated if changes are made to its tariff plans:
- tariff plan or option parameters are changed;
- tariff plans or options are added;
- tariff plans or options are removed.
In case of such changes, update the SaaS application configuration in Marketplace:
-
Edit the JSON file
catalog_<SERVICE_NAME>.jsonwith the service configuration description.-
To keep access to the currently published service revision in Marketplace test namespaces, insert an additional section into the JSON file to describe the new service configuration.
-
Make sure that the JSON file retains all sections describing the published service revisions.
-
Make sure that the new service configuration specifies a new service revision. If the specified service revision has already been uploaded to Marketplace, the service will not be updated.
-
If you have changed the parameters of the current tariff plans, make sure that the new service configuration specifies new plan revisions. If the specified plan revisions have already been uploaded to Marketplace, the tariff plans will not be updated.
-
-
If you have added or removed tariff plans, edit the
resources/plan_mapping.jsonfile in the broker directory.Since the broker periodically sends the list of service configurations to Marketplace, the new configuration will automatically appear in the Marketplace test namespace.
-
Test the new service revision in the Marketplace test namespace.
-
Go to the Marketplace section of the VK Cloud management console.
-
Click the All solutions button.
-
Click your service's card and go to the Pricing plans tab.
-
Make sure the configuration wizard for each pricing plan is displayed correctly.
-
Connect the service.
-
Update the service instance:
- Change the values of the pricing options of the current pricing plan.
- Switch to a new pricing plan.
-
Test the main user scenarios of the service.
-
Delete the service instance.
-
-
If necessary, make changes to the configuration of the new service revision:
- Navigate to the
resourcessubdirectory of the broker directory. - Edit the
catalog_<SERVICE_NAME>.jsonandplan_mapping.jsonfiles. - Repeat testing once more.
- Navigate to the
-
If you specified test cost values in the new revision for the duration of testing and debugging, edit the
catalog_<SERVICE_NAME>.jsonfile to specify the real values. -
Publish the new service revision in the open Marketplace namespace. To do this, send an email to marketplace@cloud.vk.com. In the email, specify the service ID and its new revision.
The service configuration will be moderated. After that, the new service revision will move from the Marketplace test namespace to the open namespace specified in the
metadataparameter in the service configuration JSON file. The new service revision will be available to all users who have access to this open namespace.The previously published revision will move to the Marketplace test namespace. All unpublished revisions described in the service configuration JSON file are retained in the test namespaces.
Service revisions removed from the service configuration will not be available in either the test or open Marketplace namespaces.
Publishing a new revision will not affect the already existing service instances (tenants/accounts). The revision of these service instances will not change, even if it has been removed from the service configuration and is no longer available in Marketplace.