I am getting the following airbyte for an airbyte yaml ui connector:

Traceback (most recent call last):
  File "/home/airbyte/.pyenv/versions/3.10.15/lib/python3.10/site-packages/airbyte_cdk/sources/declarative/manifest_declarative_source.py", line 243, in _validate_source
    validate(self._source_config, declarative_component_schema)
  File "/home/airbyte/.pyenv/versions/3.10.15/lib/python3.10/site-packages/jsonschema/validators.py", line 1121, in validate
    raise error
jsonschema.exceptions.ValidationError: 'HttpRequester' is not one of ['CustomRequester']

Failed validating 'enum' in schema[0]['properties']['type']:
    {'enum': ['CustomRequester'], 'type': 'string'}

On instance['type']:
    'HttpRequester'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/airbyte/.pyenv/versions/3.10.15/lib/python3.10/site-packages/airbyte_cdk/connector_builder/main.py", line 101, in <module>
    print(handle_request(sys.argv[1:]))
  File "/home/airbyte/.pyenv/versions/3.10.15/lib/python3.10/site-packages/airbyte_cdk/connector_builder/main.py", line 91, in handle_request
    source = create_source(config, limits)
  File "/home/airbyte/.pyenv/versions/3.10.15/lib/python3.10/site-packages/airbyte_cdk/connector_builder/connector_builder_handler.py", line 54, in create_source
    return ManifestDeclarativeSource(
  File "/home/airbyte/.pyenv/versions/3.10.15/lib/python3.10/site-packages/airbyte_cdk/sources/declarative/manifest_declarative_source.py", line 91, in __init__
    self._validate_source()
  File "/home/airbyte/.pyenv/versions/3.10.15/lib/python3.10/site-packages/airbyte_cdk/sources/declarative/manifest_declarative_source.py", line 245, in _validate_source
    raise ValidationError(
jsonschema.exceptions.ValidationError: Validation against json schema defined in declarative_component_schema.yaml schema failed

This error is coming from JSON Schema validation of your declarative YAML manifest, not from the runtime HTTP call itself. From the docs, the only built‑in requester type in the declarative YAML is

HttpRequester

, and its schema looks like this:

Requester -> HttpRequester

with

type

implicitly being

HttpRequester

and supporting properties like

url_base

,

path

,

http_method

, etc.[[Requester docs](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/requester); [Next Requester](https://docs.airbyte.com/platform/next/connector-development/config-based/understanding-the-yaml-file/requester)] Your error says:

text Failed validating 'enum' in schema[0]['properties']['type']:     {'enum': ['CustomRequester'], 'type': 'string'}  On instance['type']:     'HttpRequester'

This means that, in the schema that is being used to validate your manifest, the

type

field for that component is restricted to the single value

CustomRequester

(via an

enum

), but your YAML has

type: HttpRequester

. Airbyte enforces that

enum

values must match exactly and be unique.[[Using enum](https://docs.airbyte.com/platform/connector-development/connector-specification-reference#using-enum); [Next enum](https://docs.airbyte.com/platform/next/connector-development/connector-specification-reference#using-enum)] Based on the provided knowledge sources, I cannot see the definition of

CustomRequester

or how it is supposed to be used, so I can’t give a precise fix for that custom type. However, the root cause is clear: - The declarative schema you are validating against only allows

type: CustomRequester

for that requester. - Your manifest uses

type: HttpRequester

, which is rejected by that schema. To move forward, you have two options, depending on what you intend: 1. Use the standard declarative HTTP requester Ensure your YAML requester block follows the documented

HttpRequester

shape and that the schema you are using actually allows

HttpRequester

as a valid

type

. For example (conceptually):

yaml    requester:      type: HttpRequester      url_base: "<https://api.example.com/>"      path: "/endpoint"      http_method: GET

If your current schema only has

enum: ['CustomRequester']

, it would need to be updated to also allow

HttpRequester

(e.g.,

enum: ['HttpRequester', 'CustomRequester']

), but the knowledge sources do not show how to modify that schema, so I cannot provide exact steps. 2. Use your custom requester If your project intentionally defines a

CustomRequester

and the schema is correct, then your YAML should use

type: CustomRequester

and follow whatever properties that custom type expects. The knowledge sources do not document

CustomRequester

, so I can’t show a valid example or its required fields. Because the knowledge sources only document

HttpRequester

and do not describe

CustomRequester

or how to extend the schema, I’m limited to identifying the mismatch between your manifest (

HttpRequester

) and the validating schema (

CustomRequester

only). To resolve the error, you’ll need to align: - the

type

value in your YAML, and - the

enum

allowed values in the schema being used for validation.