With this change we have to perform a release to the CLI tool and maintain
the both versions of CLI tool to support old product versions and later
versions. Let's track those changes as well.
On Thu, Aug 15, 2019 at 3:12 PM Malintha Amarasinghe
wrote:
>
>
> On Thu, Aug 15, 2019 at 9:03 AM Isha
On Thu, Aug 15, 2019 at 9:03 AM Ishara Cooray wrote:
> Hi,
>
> We can move the same functionality to the "*POST
> /import/api?preserveProvider={false} -F file={@api.zip}*" API with
> another optional query parameter "*isOverwrite*" to update an existing
> API. Instead of giving the APIID to upda
Hi,
We can move the same functionality to the "*POST
/import/api?preserveProvider={false} -F file={@api.zip}*" API with another
optional query parameter "*isOverwrite*" to update an existing API. Instead
of giving the APIID to update, can't we get the existing API using the
name, version, and ten
Hi all,
After we decided to go ahead with the import-export approach, we decided to
move the existing api-import-export APIs to Admin REST APIs (similar to
current application-import-export APIs). So the Admin REST API will have
the following two new resources.
*GET
/export/api?name={APIName}&ver
On Tue, Aug 6, 2019 at 9:35 PM Dushani Wellappili wrote:
> Hi all,
>
> When publishing to external stores, at runtime we need to use API create,
> life-cycle change, create a version, add API thumbnail, delete Publisher
> REST APIs. In order to create the API payload, we need to do the mapping
>
