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
+44Lines changed: 44 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1793,6 +1793,44 @@ definitions:
1793
1793
$parameters:
1794
1794
type: object
1795
1795
additionalProperties: true
1796
+
1797
+
PropertyTypesMap:
1798
+
title: Types Map
1799
+
description: (This component is experimental. Use at your own risk.) Represents a mapping between a current type and its corresponding target type for property.
1800
+
type: object
1801
+
required:
1802
+
- property_name
1803
+
- property_type_pinter
1804
+
- type_mapping
1805
+
properties:
1806
+
property_name:
1807
+
type: string
1808
+
property_type_pointer:
1809
+
title: Key Path
1810
+
description: List of potentially nested fields describing the full path of the property type to extract.
1811
+
type: array
1812
+
items:
1813
+
- type: string
1814
+
type_mapping:
1815
+
"$ref": "#/definitions/TypesMap"
1816
+
ItemsTypeMap:
1817
+
title: Types Map
1818
+
description: (This component is experimental. Use at your own risk.) Represents a mapping between a current type and its corresponding target type for property.
1819
+
type: object
1820
+
required:
1821
+
- items_type_pinter
1822
+
- type_mapping
1823
+
properties:
1824
+
property_name:
1825
+
type: string
1826
+
items_type_pointer:
1827
+
title: Items Type Path
1828
+
description: List of potentially nested fields describing the full path of the items type to extract.
1829
+
type: array
1830
+
items:
1831
+
- type: string
1832
+
type_mapping:
1833
+
"$ref": "#/definitions/TypesMap"
1796
1834
TypesMap:
1797
1835
title: Types Map
1798
1836
description: (This component is experimental. Use at your own risk.) Represents a mapping between a current type and its corresponding target type.
@@ -1817,6 +1855,12 @@ definitions:
1817
1855
type: string
1818
1856
interpolation_context:
1819
1857
- raw_schema
1858
+
items_type:
1859
+
"$ref": "#/definitions/ItemsTypeMap"
1860
+
properties_types:
1861
+
type: array
1862
+
items:
1863
+
- "$ref": "#/definitions/PropertyTypesMap"
1820
1864
SchemaTypeIdentifier:
1821
1865
title: Schema Type Identifier
1822
1866
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