Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

Version 1 Current »

We created an 'om_releases' table in App Manager for storing Application Resource URL/Endpoint, Application Type(Popflow, Config, Data API, Queue Adapter, etc) and Version. These details will be used on the Provisioning screen when user is going to add an Application Resource to provision a new Customer. He will be able to select the version for each Application resource based on the data inside the 'om_releases' table.

To add entries into the ‘om_releases' table, we need to use the following API: '/api/v2/provisioning/application/release’. This API will be called from outside of App Manager. It could be a pipeline or an independent User Interface.

Instructions

  • The API for saving a new Application Release is: /api/v2/provisioning/application/release. This is a POST end point.

  • You will need to send a request object containing following fields: ‘version’, ‘applicationType’ and ‘endpoint’.

  • ‘applicationType' denotes the type of Application Resource.

Enter values between 1 to 5.

1: ‘HarmonyClient’,

2: ‘Popflow’,

3: ‘Config’,

4: ‘DataApi’ and

5: 'QueueAdpater’.

  • 'endpoint' denotes the URL of the Application Resource.

  • 'version' denotes which version of the Application Resource you want to set.