carbon-apimgt icon indicating copy to clipboard operation
carbon-apimgt copied to clipboard

Add: Support Custom Sequence as a Backend of an API

Open BLasan opened this issue 6 months ago • 5 comments

Purpose

Some API developers want to use connectors within the api manager to implement mediation logic as they do not want to use an additional MI deployment if their use cases are simple. Within the API Manager, currently, we do not have a construct that will allow us to facilitate this requirement.

Approach

  1. Provide a new Endpoint Type "Sequence Backend" for REST APIs under Endpoint Tab
  2. Allow Sequences to be added for Sandbox and Production Key types separately,.
  3. Perform download, delete, upload operations for Sequence Backends.
  4. Add support for APICTL import and export scenarios for REST APIs
  5. Introduced a new table to store Sequence Backend. Following is the schema for the table.
CREATE TABLE IF NOT EXISTS AM_API_SEQUENCE_BACKEND (
  ID VARCHAR(60) NOT NULL,
  API_UUID VARCHAR(256) NOT NULL,
  REVISION_UUID VARCHAR(256) DEFAULT '0',
  SEQUENCE LONGBLOB NOT NULL,
  NAME VARCHAR(256) NOT NULL,
  TYPE VARCHAR(120) NOT NULL,
  PRIMARY KEY (ID),
  FOREIGN KEY (API_UUID) REFERENCES AM_API(API_UUID) ON DELETE CASCADE
)ENGINE INNODB;

Affected Flows

Please refer - https://github.com/wso2/api-manager/issues/3007#issuecomment-2336934254

Issue

  • https://github.com/wso2/api-manager/issues/3007

BLasan avatar Aug 25 '24 17:08 BLasan