@aifabrix/builder 2.52.1 → 2.53.1

package/integration/github/github-system.json

@@ -1,82 +0,0 @@
-{
-  "key": "github",
-  "displayName": "GitHub",
-  "description": "Production GitHub REST integration: repository issues (list/create/update/close), issue comments, and repository lifecycle operations. Uses Miso apiProvider github with GitHub App expiring user tokens.",
-  "type": "custom",
-  "enabled": true,
-  "authentication": {
-    "authType": "apiProvider",
-    "apiProvider": {
-      "apiProviderKey": "github"
-    }
-  },
-  "configuration": [
-    {
-      "name": "BASE_URL",
-      "value": "https://api.github.com",
-      "location": "variable",
-      "required": true
-    },
-    {
-      "name": "GITHUB_OWNER",
-      "value": "{{GITHUB_OWNER}}",
-      "location": "variable",
-      "required": true,
-      "portalInput": {
-        "field": "text",
-        "label": "GitHub repository owner",
-        "placeholder": "Organization or user login (e.g. octocat)",
-        "validation": {
-          "required": true,
-          "minLength": 1
-        }
-      }
-    },
-    {
-      "name": "GITHUB_REPO",
-      "value": "{{GITHUB_REPO}}",
-      "location": "variable",
-      "required": true,
-      "portalInput": {
-        "field": "text",
-        "label": "GitHub repository name",
-        "placeholder": "Repository name without owner (e.g. Hello-World)",
-        "validation": {
-          "required": true,
-          "minLength": 1
-        }
-      }
-    }
-  ],
-  "endpoints": [
-    {
-      "type": "issues",
-      "path": "/issues",
-      "description": "GitHub repository issues",
-      "active": true
-    },
-    {
-      "type": "comments",
-      "path": "/comments",
-      "description": "GitHub issue comments",
-      "active": true
-    }
-  ],
-  "endpointsActive": true,
-  "dataSources": [
-    "github-issues",
-    "github-issue-comments",
-    "github-repository"
-  ],
-  "certification": {
-    "enabled": true,
-    "publicKey": "-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtwvWqPVKNUCLAmBIrK0u\nrsxzgtvIiyIFQVc+T5FeBYevUDOoS2VBF0aOCJGGV8P+ARzU7PtaTCZYvRvsmqou\namy+c1+b0kGCObh/gxGGVCFmbH4VCfQ2xkwML8vvAHXBW1v9Abu9EuTv3YpIZUSh\nq+0xuivs3xYwq5Lm/K10WaWzfwbjCND0K7aQmNhQq+n45EjgmkEWV2gQUDyALzsW\nfTikMtbBJEQ8BSCN8uOsZsa8MH2bBFgThIUXX/gxeUIEBfEavi8F3eR2ZC+Q/if2\nJkIwUCcH5nN2jTCDZgt5CLTIhYs51A+1kLTjtCmJ2fMmeV7Wr3DgnzdbM1cHRnT+\nlwIDAQAB\n-----END PUBLIC KEY-----",
-    "algorithm": "RS256",
-    "issuer": "Dataplane - community edition",
-    "version": "1.0.0",
-    "status": "passed",
-    "level": "SILVER",
-    "publicKeyFingerprint": "sha256:e14a67b980051e46d6b15e2c42c57aea6328d8c96622d10f01e4f9c2f22af3c5",
-    "contractHash": "sha256:70531b5131122bd8b93c948dc93506b9d3cce5fe28efa4a28d136022f834ccc5"
-  }
-}

package/integration/hubspot-test/README.md

@@ -1,159 +0,0 @@
-# HubSpot CRM
-
-HubSpot CRM integration with OpenAPI support for companies, contacts, and deals
-
-## System Information
-
-- **System Key**: `hubspot-test`
-- **System Type**: `openapi`
-- **Datasources**: 4
-
-## Regenerating files with the CLI (recommended)
-
-Datasource and system JSON under this folder are **normally produced by the Builder**, not edited by hand for structural/schema changes. Use one of these flows (from the **repository root**):
-
-1. **Interactive wizard** (writes to `integration/hubspot-test/` when the app key is `hubspot-test`):
-
-   ```bash
-   aifabrix wizard hubspot-test
-   ```
-
-2. **Headless wizard – known platform HubSpot** (same folder; needs dataplane + auth):
-
-   ```bash
-   node bin/aifabrix.js wizard \
-     --config integration/hubspot-test/wizard-hubspot-test-headless.yaml \
-     --controller <YOUR_CONTROLLER_URL> \
-     --environment <YOUR_ENV>
-   ```
-
-   Edit `deployment.controller` / `deployment.environment` in that YAML if you prefer not to pass flags.
-
-3. **Helper script** (generates a temporary wizard config and runs the CLI; defaults OpenAPI to `companies.json` in this directory):
-
-   ```bash
-   node integration/hubspot-test/create-hubspot.js --name hubspot-test --keep-wizard-files
-   ```
-
-After regeneration, run `aifabrix validate hubspot-test --type external` and the HubSpot integration tests as needed.
-
-Committed copies may still be **trimmed or adjusted** for repo tests (e.g. deterministic fields); prefer changing **generators/templates** in `lib/` and `templates/` when defaults should change for everyone.
-
-## Files
-
-- `application.yaml` – Application configuration with `app` and `externalIntegration` blocks
-- `hubspot-test-system.json` – External system definition (authentication, OpenAPI/MCP, RBAC)
-- `hubspot-test-datasource-deal.json` – Datasource: HubSpot Deal
-- `hubspot-test-datasource-contact.json` – Datasource: HubSpot Contact
-- `hubspot-test-datasource-users.json` – Datasource: HubSpot Users
-- `hubspot-test-datasource-company.json` – Datasource: HubSpot Company
-- `env.template` – Environment variables template (secrets, API keys)
-- `hubspot-test-deploy.json` – Deployment manifest (generated by `aifabrix json`)
-
-Optional: `rbac.yaml` – Roles and permissions merged into the system when present.
-
-## Quick Start
-
-### 1. Create External System
-
-```bash
-aifabrix create hubspot-test
-```
-
-(External is the default type. Use `aifabrix create <name> --type webapp` for a builder app.)
-
-Or use the interactive wizard:
-
-```bash
-aifabrix wizard --app hubspot-test
-```
-
-### 2. Configure Authentication and Datasources
-
-Edit files in `integration/hubspot-test/`:
-
-- **Authentication**: `hubspot-test-system.json` (auth type, credentials placeholders)
-- **Field mappings**: `hubspot-test-datasource-*.json` (dimensions, attributes, operations)
-
-### 3. Validate Configuration
-
-```bash
-aifabrix validate hubspot-test --type external
-```
-
-### 4. Generate Deployment Manifest
-
-```bash
-aifabrix json hubspot-test --type external
-```
-
-This creates `hubspot-test-deploy.json` in `integration/hubspot-test/`.
-
-### 5. Deploy
-
-Controller URL and environment are read from config. Configure and log in first:
-
-```bash
-aifabrix auth config --set-controller <url> --set-environment dev
-aifabrix login
-```
-
-Then deploy:
-
-```bash
-aifabrix deploy hubspot-test
-```
-
-## Testing
-
-### Unit Tests (Local Validation, No API)
-
-```bash
-aifabrix test hubspot-test
-```
-
-### Integration Tests (Via Dataplane)
-
-```bash
-aifabrix test-integration hubspot-test
-```
-
-## Deployment
-
-Deploy via miso-controller pipeline (same as regular apps). Auth and controller come from `aifabrix login` and `aifabrix auth config`:
-
-```bash
-aifabrix deploy hubspot-test
-```
-
-## Wizard E2E tests (`test.js`)
-
-Run positive wizard tests with:
-
-```bash
-pnpm run test:hubspot-wizard -- --type positive
-```
-
-If you see **"Invalid token or insufficient permissions"** or **"Failed to create wizard session"** even though `aifabrix auth status` shows connected, the dataplane may be configured to accept only **client credentials** for the wizard API, not device tokens.
-
-**Option A – Use client credentials (recommended if dataplane requires them)**
-
-1. Get a **client ID** and **client secret** for an app that the dataplane accepts for wizard (e.g. from your admin or Miso/Keycloak for the environment).
-2. Put them in **`~/.aifabrix/secrets.local.yaml`** under keys that depend on the **app name in the wizard config**:
-   - For `wizard-hubspot-e2e.yaml` the app name is `wizard-e2e-e2e`, so use:
-     - `wizard-e2e-e2e-client-idKeyVault`: `<your client id>`
-     - `wizard-e2e-e2e-client-secretKeyVault`: `<your client secret>`
-   - If your platform uses a single “wizard” or “dataplane” app for all wizard runs, ask your admin for that app’s client ID/secret and the exact key names (they may be something like `dataplane-client-idKeyVault` / `dataplane-client-secretKeyVault`; the builder looks up `<appName>-client-idKeyVault` and `<appName>-client-secretKeyVault` where `appName` comes from the config file).
-3. **Optional fallback:** you can also set **`integration/hubspot-test/.env`** with `CLIENTID` and `CLIENTSECRET`; the test runner maps those to `HUBSPOT_CLIENT_ID` / `HUBSPOT_CLIENT_SECRET` for real-credential tests, and the token manager uses `CLIENTID`/`CLIENTSECRET` when no secrets file entry exists for the app.
-
-**Option B – Use device token**
-
-If the dataplane is configured to accept device tokens for the wizard API, ensure you are logged in with `aifabrix login` and that the controller URL and environment match (e.g. `dev`). No client credentials are needed.
-
-When this error appears, `pnpm test:hubspot-wizard` **skips** the live wizard cases (exit code 0) so optional CI/agents are not blocked; configure client credentials or dataplane auth to run those cases for real.
-
-## Troubleshooting
-
-- **Validation errors**: Run `aifabrix validate hubspot-test --type external` to see schema and manifest errors.
-- **Deployment / auth**: Run `aifabrix auth config --set-controller <url> --set-environment <env>` and `aifabrix login` before `aifabrix deploy`.
-- **File not found**: Run commands from the project root (where `package.json` and `integration/` live).

package/integration/hubspot-test/application.json

@@ -1,54 +0,0 @@
-{
-  "app": {
-    "key": "hubspot-test",
-    "displayName": "HubSpot CRM",
-    "description": "HubSpot CRM integration with OpenAPI support for companies, contacts, and deals",
-    "type": "external"
-  },
-  "externalIntegration": {
-    "schemaBasePath": "./",
-    "systems": [
-      "hubspot-test-system.json"
-    ],
-    "dataSources": [
-      "hubspot-test-datasource-company.json",
-      "hubspot-test-datasource-contact.json",
-      "hubspot-test-datasource-deal.json",
-      "hubspot-test-datasource-users.json"
-    ],
-    "autopublish": true,
-    "version": "1.0.0"
-  },
-  "configuration": [
-    {
-      "name": "HUBSPOT_API_VERSION",
-      "portalInput": {
-        "field": "select",
-        "label": "HubSpot API Version",
-        "placeholder": "Select API version",
-        "options": [
-          "v1",
-          "v2",
-          "v3"
-        ],
-        "validation": {
-          "required": false
-        }
-      }
-    },
-    {
-      "name": "MAX_PAGE_SIZE",
-      "portalInput": {
-        "field": "text",
-        "label": "Maximum Page Size",
-        "placeholder": "100",
-        "validation": {
-          "required": false,
-          "pattern": "^[0-9]+$",
-          "minLength": 1,
-          "maxLength": 1000
-        }
-      }
-    }
-  ]
-}