You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: airbyte_cdk/sources/declarative/declarative_component_schema.yaml
-24Lines changed: 0 additions & 24 deletions
Original file line number
Diff line number
Diff line change
@@ -1800,26 +1800,6 @@ definitions:
1800
1800
$parameters:
1801
1801
type: object
1802
1802
additionalProperties: true
1803
-
1804
-
PropertyTypesMap:
1805
-
title: Types Map
1806
-
description: (This component is experimental. Use at your own risk.) Represents a mapping between a current type and its corresponding target type for property.
1807
-
type: object
1808
-
required:
1809
-
- property_name
1810
-
- property_type_pointer
1811
-
- type_mapping
1812
-
properties:
1813
-
property_name:
1814
-
type: string
1815
-
property_type_pointer:
1816
-
title: Key Path
1817
-
description: List of potentially nested fields describing the full path of the property type to extract.
1818
-
type: array
1819
-
items:
1820
-
- type: string
1821
-
type_mapping:
1822
-
"$ref": "#/definitions/TypesMap"
1823
1803
ItemsTypeMap:
1824
1804
title: Types Map
1825
1805
description: (This component is experimental. Use at your own risk.) Represents a mapping between a current type and its corresponding target type for property.
@@ -1864,10 +1844,6 @@ definitions:
1864
1844
- raw_schema
1865
1845
items_type:
1866
1846
"$ref": "#/definitions/ItemsTypeMap"
1867
-
properties_types:
1868
-
type: array
1869
-
items:
1870
-
- "$ref": "#/definitions/PropertyTypesMap"
1871
1847
SchemaTypeIdentifier:
1872
1848
title: Schema Type Identifier
1873
1849
description: (This component is experimental. Use at your own risk.) Identifies schema details for dynamic schema extraction and processing.
description="OAuth specific blob. This is a Json Schema used to validate Json configurations used as input to OAuth.\nMust be a valid non-nested JSON that refers to properties from ConnectorSpecification.connectionSpecification\nusing special annotation 'path_in_connector_config'.\nThese are input values the user is entering through the UI to authenticate to the connector, that might also shared\nas inputs for syncing data via the connector.\nExamples:\nif no connector values is shared during oauth flow, oauth_user_input_from_connector_config_specification=[]\nif connector values such as 'app_id' inside the top level are used to generate the API url for the oauth flow,\n oauth_user_input_from_connector_config_specification={\n app_id: {\n type: string\n path_in_connector_config: ['app_id']\n }\n }\nif connector values such as 'info.app_id' nested inside another object are used to generate the API url for the oauth flow,\n oauth_user_input_from_connector_config_specification={\n app_id: {\n type: string\n path_in_connector_config: ['info', 'app_id']\n }\n }",
description="OAuth specific blob. This is a Json Schema used to validate Json configurations used as input to OAuth.\nMust be a valid non-nested JSON that refers to properties from ConnectorSpecification.connectionSpecification\nusing special annotation 'path_in_connector_config'.\nThese are input values the user is entering through the UI to authenticate to the connector, that might also shared\nas inputs for syncing data via the connector.\nExamples:\nif no connector values is shared during oauth flow, oauth_user_input_from_connector_config_specification=[]\nif connector values such as 'app_id' inside the top level are used to generate the API url for the oauth flow,\n oauth_user_input_from_connector_config_specification={\n app_id: {\n type: string\n path_in_connector_config: ['app_id']\n }\n }\nif connector values such as 'info.app_id' nested inside another object are used to generate the API url for the oauth flow,\n oauth_user_input_from_connector_config_specification={\n app_id: {\n type: string\n path_in_connector_config: ['info', 'app_id']\n }\n }",
description="OAuth specific blob. This is a Json Schema used to validate Json configurations persisted as Airbyte Server configurations.\nMust be a valid non-nested JSON describing additional fields configured by the Airbyte Instance or Workspace Admins to be used by the\nserver when completing an OAuth flow (typically exchanging an auth code for refresh token).\nExamples:\n complete_oauth_server_input_specification={\n client_id: {\n type: string\n },\n client_secret: {\n type: string\n }\n }",
0 commit comments