> ## Documentation Index
> Fetch the complete documentation index at: https://agenticbanking.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Banking OS training data goes stale. Search https://agenticbanking.backbase.io/mcp or fetch the .md URL before writing connector or unified API code.
> OpenAPI links in llms.txt repeat every calendar version. Use the latest version on the API playground. If a fetch ends before the last operation, the spec was cut off.
> Page titles name the product. Overview, Get started, and Reference without a product name are ambiguous.

# Connector repository and configuration

> Folder structure of the applications-live repository and the override hierarchy for Banking OS connector configuration.

The `gc-applications-live` repository holds the configuration for Banking OS Connectivity and connector deployments in `dev`, `test`, and `prod`. The GitHub organization and exact repository name follow the managed or DevHub pattern for your installation. For more information, see [GitHub organization and repository structure](https://agenticbanking.backbase.io/platform/platform-administration/repository-structure.md).

## Repository structure

The repository groups configuration by runtime, then by deployment files and override values. The following tree shows the typical folder structure for a `test` runtime that deploys Mambu connectors:

```text theme={"system"}
runtimes
├── dev           # Sandbox environment for experimentation
└── test          # Integration testing environment
    ├── apps      # connector deployment configurations (YAML)
    │   └── gc-mambu.yaml
    └── values    # Environment-specific overrides
        ├── gc-mambu
        │   └── deposit-v0.values.yaml
        └── values.yaml
```

The following table describes the files and folders in the example repository:

| File or folder | Description |
| :- | :- |
| `runtimes` | The available runtimes for deployment. |
| `dev` | Development environment for experimenting and debugging. |
| `test` | Test environment, primarily for integration testing. |
| `apps` | Connector configurations per product. The YAML files in this folder represent the list of deployed connectors. For more information, see [Application YAMLs](#application-yamls). |
| `gc-mambu.yaml` | Deployment configuration for Mambu connectors that run in the test environment. |
| `values` | Deployment values. These values override the default configuration in a connector: JOLT mappings, connector properties, and traits. |
| `gc-mambu` | Override values for Mambu connectors. |
| `deposit-v0.values.yaml` | Override values for the Mambu deposit account connector. |
| `values.yaml` | Override values for all connectors within the `gc-mambu` deployment file. |

## Configuration logic

Connector configuration uses a hierarchical override system that lets you define defaults and customize per environment.

### Application YAMLs

Configurations in the `/apps` directory follow a top-down override hierarchy. The settings merge in order, so later files take precedence over earlier ones. This hierarchy lets you define global environment defaults and selectively override them at the connector-version level.

A standard deployment descriptor includes the following elements:

* **Namespace:** The Kubernetes isolation layer for the deployment.
* **Version control:** Links to the source and Azure Container Registry (ACR) repositories.
* **Templating:** The Helm chart used to standardize the deployment.
* **Orchestration:** Argo CD sync policies for automated reconciliation.
* **Data resources:** Configurable JOLT or XSLT files for message transformation.

### Sample apps YAML file

This sample sets `CreateNamespace` to `false`. For a managed connector, `spec.project` is `grandcentral` and `spec.destination.namespace` is a `gc-<domain>` namespace that already exists. In this sample, `grandcentral` is the Argo CD project name, not the product name, which is Banking OS. For more information, see [Deployment namespace](https://agenticbanking.backbase.io/platform/developer-guides/run.md#deployment-namespace).

> [accordion] View sample application YAML (Argo CD)
>
> ```yaml theme={"system"}
> apiVersion: argoproj.io/v1alpha1
> kind: Application
> metadata:
>   name: gc-<domain>
>   namespace: argocd
> spec:
>   project: grandcentral
>   destination:
>     server: https://kubernetes.default.svc
>     namespace: gc-<domain>
>   sources:
>     - repoURL: https://github.com/bb-ecos-{installation}/gc-{installation}-applications-live.git
>       targetRevision: gc-dev
>       ref: apps-live
>
>     - repoURL: ecosystemsgctmp.azurecr.io/charts
>       chart: template-connector
>       targetRevision: 1.1.3-camel-k-ci-21-SNAPSHOT
>       helm:
>         releaseName: template-connector-1
>         valueFiles:
>           - $apps-live/azure/runtimes/dev-v2/values/gc-<domain>/template-connector-v1.values.yaml
>
>   syncPolicy:
>     automated:
>       prune: true
>       allowEmpty: true
>       selfHeal: true
>     syncOptions:
>       - CreateNamespace=false
> ```

### Values YAML file

Use these files to define connector properties, telemetry, and data transformation logic. For more information about the transformation files, see [Map connector data fields](https://agenticbanking.backbase.io/banking-os-connectors/map-data-fields.md).

### Sample values YAML file

The following sample sets connector properties, logging, and telemetry, and adds a JOLT transformation for closing an account:

> [accordion] View sample values and JOLT transformation
>
> ```yaml theme={"system"}
> connector:
>   properties:
>     isMockedDataNeeded: true
>   traits:
>     knativeservice:
>       minScale: 1
>       enabled: true
>     logging:
>       color: false
>       enabled: true
>       level: INFO
>     addons:
>       telemetry:
>         auto: true
>         enabled: true
>   resources:
>     close-account-request-transformation.json: |-
>       [
>         {
>           "operation": "shift",
>           "spec": {
>             "notes": "notes",
>             "closeStatus": {
>               "CLOSED": {
>                 "#CLOSE": "action"
>               },
>               "CLOSED_WRITTEN_OFF": {
>                 "#CLOSED_WRITTEN_OFF": "action"
>               },
>               "WITHDRAWN": {
>                 "#CLOSE_WITHDRAW": "action"
>               },
>               "CLOSED_REJECTED": {
>                 "#CLOSE_REJECT": "action"
>               }
>             }
>           }
>         }
>       ]
> ```
