@teamfabric/create-fabric-connector NPM

create-fabric-connector

A CLI to bootstrap new connectors

Usage

npx create-fabric-connector

You can also use arguments to skip the cli as:

--name || -n

--domain || -d

--spec || -s

npx @teamfabric/create-fabric-connector -n fabric-integration-authorizenet-v2 -d b2c_payment -s /path/to/file/spec_files/b2c-payments_v1.yaml

the folder for the new connector will be ./connector-name

#Required files changes to individual connector.

In .gitlab-ci.yml file:

variables:
  DOMAIN: "domain_name"
  CONNECTOR_NAME: "connector_name"

In serverless.yml file:

service:
  name: connector name

environment:
    CONNECTOR_NAME: ${env:CONNECTOR_NAME,'connector_name'}
    DOMAIN_NAME: ${env:DOMAIN_NAME,'domain_name'}

Add SonarCloud Properties to sonar cloud.
In connector_config.json file:
```
"name": "connector_name",
  "domainName": "domain_name",
```
Also set the supportedActions entry according with was set in the Connector Configurator
In webpack.config.js the line 19 with the filename entry , should have :
```
filename: "[name].js",
```
like in
```
  output: {
    libraryTarget: "commonjs",
    path: path.join(__dirname, ".webpack"),
    filename: "[name].js",
  },
```
Notes
- The connector_name and domain_name should be the exact same way they are in the Connector Configurator. Ideally they should be lowercase with no space
- The scaffolding code, runs with the node 14 version, using most recent version there is an issue with Endpoint that are not usingthe GET verb.
- To deploy this code to uat and prod environments, it is necessary create a MR to the main branch, After this is merged, a pipeline will be created, And the buttonms to maually deploy to uat(sandbox) and prod will be available
- For each environment deployed, it is necessary to do some points: Create the secrets with the Connector Configurator url and api-key Create the domain (if is not created yet) and the connector entries in the connector configurator of the environment