@kapa.ai am new to building airbyte source and destination connectors. building one for couchbase. Could you please tell me the difference between manifest.yaml, spec.yaml, spec.json and metadata.yaml

New message text here

@kapa.ai Can you give me some samples of each for Couchbase

A message from kapa.ai

I'm sorry, but the provided knowledge sources do not contain specific examples or samples for Couchbase for

manifest.yaml

,

spec.yaml

,

spec.json

, and

metadata.yaml

files. However, I can provide you with general examples and you would need to adjust them according to your specific needs for Couchbase. Here are some general examples: 1. `manifest.yaml`: This is a general example and does not specifically pertain to Couchbase. You would need to adjust the details according to your Couchbase connector.

yaml version: "0.1.0"   definitions:     <key-value pairs defining objects which will be reused in the YAML connector>   streams:     <list stream definitions>   check:     <definition of connection checker>   spec:     <connector spec>

[Source](https://docs.airbyte.com/connector-development/config-based/low-code-cdk-overview#configuring-the-yaml-file) 2.

spec.yaml

or `spec.json`: This is a general example and does not specifically pertain to Couchbase. You would need to adjust the details according to your Couchbase connector.

json {   "documentationUrl": "<https://docs.airbyte.com/integrations/sources/dremio>",   "connectionSpecification": {     "$schema": "<http://json-schema.org/draft-07/schema#>",     "title": "Dremio Source Spec",     "type": "object",     "required": ["host", "port", "username", "password", "database", "schema"],     "additionalProperties": false,     "properties": {       "host": {         "type": "string",         "description": "Hostname of the database."       },       ...     }   } }

[Source](https://docs.airbyte.com/connector-development/tutorials/the-hard-way/build-a-connector-the-hard-way#implement-the-spec-operation) 3. `metadata.yaml`: This is a general example and does not specifically pertain to Couchbase. You would need to adjust the details according to your Couchbase connector.

yaml data:     allowedHosts:       hosts:         - ${host}         - ${tunnel_method.tunnel_host}     connectorSubtype: database     connectorType: source     definitionId: decd338e-5647-4c0b-adf4-da0e75f5a750     dockerImageTag: 2.0.28     maxSecondsBetweenMessages: 7200     dockerRepository: airbyte/source-postgres     githubIssueLabel: source-postgres     icon: postgresql.svg     license: MIT     name: Postgres     tags:       - language:java       - language:python     registries:       cloud:         dockerRepository: airbyte/source-postgres-strict-encrypt         enabled: true       oss:         enabled: true     supportLevel: certified     documentationUrl: <https://docs.airbyte.com/integrations/sources/postgres>   metadataSpecVersion: "1.0"

[Source](https://docs.airbyte.com/connector-development/connector-metadata-file) Please note that these are just examples and you would need to adjust them according to your specific needs for Couchbase.

@kapa.ai okay give me some templates

A message from kapa.ai

Sure, here are some general templates for the files you asked about: 1. `manifest.yaml`:

yaml version: "0.1.0"   definitions:     <key-value pairs defining objects which will be reused in the YAML connector>   streams:     <list stream definitions>   check:     <definition of connection checker>   spec:     <connector spec>

2.

spec.yaml

or `spec.json`:

json {   "documentationUrl": "<URL to the connector's documentation>",   "connectionSpecification": {     "$schema": "<http://json-schema.org/draft-07/schema#>",     "title": "<Connector Name> Spec",     "type": "object",     "required": ["<required configuration field 1>", "<required configuration field 2>", "..."],     "additionalProperties": false,     "properties": {       "<configuration field 1>": {         "type": "<type of the field>",         "description": "<Description of the field>"       },       "<configuration field 2>": {         "type": "<type of the field>",         "description": "<Description of the field>"       },       ...     }   } }

3. `metadata.yaml`:

yaml data:     allowedHosts:       hosts:         - ${{host}}         - ${{tunnel_method.tunnel_host}}     connectorSubtype: <connector subtype>     connectorType: <source or destination>     definitionId: <UUID for the connector>     dockerImageTag: <version of the connector>     maxSecondsBetweenMessages: <maximum seconds between messages>     dockerRepository: <docker repository for the connector>     githubIssueLabel: <github issue label for the connector>     icon: <icon for the connector>     license: <license for the connector>     name: <name of the connector>     tags:       - language:<programming language of the connector>     registries:       cloud:         dockerRepository: <docker repository for the connector in the cloud>         enabled: true       oss:         enabled: true     supportLevel: <support level for the connector>     documentationUrl: <URL to the connector's documentation>   metadataSpecVersion: "1.0"

Please replace the placeholders with the actual values for your Couchbase connector.