airbyte-source-public-apis 0.2.0__tar.gz

airbyte-source-public-apis-0.2.0/PKG-INFO

@@ -0,0 +1,70 @@
+Metadata-Version: 2.1
+Name: airbyte-source-public-apis
+Version: 0.2.0
+Summary: Source implementation for Public Apis.
+Author: Airbyte
+Author-email: contact@airbyte.io
+Description-Content-Type: text/markdown
+Requires-Dist: airbyte-cdk
+Provides-Extra: tests
+Requires-Dist: requests-mock~=1.9.3; extra == "tests"
+Requires-Dist: pytest~=6.2; extra == "tests"
+Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
+
+# Public Apis Source
+
+This is the repository for the Public Apis configuration based source connector.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/public-apis).
+
+
+**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/public-apis)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_public_apis/spec.yaml` file.
+Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
+See `integration_tests/sample_config.json` for a sample config file.
+
+**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source public-apis test creds`
+and place them into `secrets/config.json`.
+
+
+
+**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
+```bash
+airbyte-ci connectors --name=source-public-apis build
+```
+
+An image will be built with the tag `airbyte/source-public-apis:dev`.
+
+**Via `docker build`:**
+```bash
+docker build -t airbyte/source-public-apis:dev .
+```
+
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-public-apis:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-public-apis:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-public-apis:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-public-apis:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
+```
+
+You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
+```bash
+airbyte-ci connectors --name=source-public-apis test
+```
+
+Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
+If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
+
+All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
+We split dependencies between two groups, dependencies that are:
+* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
+* required for the testing need to go to `TEST_REQUIREMENTS` list
+
+You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
+1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-public-apis test`
+2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
+3. Make sure the `metadata.yaml` content is up to date.
+4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/public-apis.md`).
+5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
+6. Pat yourself on the back for being an awesome contributor.
+7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.

airbyte-source-public-apis-0.2.0/README.md

@@ -0,0 +1,67 @@
+# Public Apis Source
+
+This is the repository for the Public Apis configuration based source connector.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/public-apis).
+
+## Local development
+
+#### Create credentials
+**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/public-apis)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_public_apis/spec.yaml` file.
+Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
+See `integration_tests/sample_config.json` for a sample config file.
+
+**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source public-apis test creds`
+and place them into `secrets/config.json`.
+
+### Locally running the connector docker image
+
+
+#### Build
+**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
+```bash
+airbyte-ci connectors --name=source-public-apis build
+```
+
+An image will be built with the tag `airbyte/source-public-apis:dev`.
+
+**Via `docker build`:**
+```bash
+docker build -t airbyte/source-public-apis:dev .
+```
+
+#### Run
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-public-apis:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-public-apis:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-public-apis:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-public-apis:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
+```
+
+## Testing
+You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
+```bash
+airbyte-ci connectors --name=source-public-apis test
+```
+
+### Customizing acceptance Tests
+Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
+If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
+
+## Dependency Management
+All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
+We split dependencies between two groups, dependencies that are:
+* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
+* required for the testing need to go to `TEST_REQUIREMENTS` list
+
+### Publishing a new version of the connector
+You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
+1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-public-apis test`
+2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
+3. Make sure the `metadata.yaml` content is up to date.
+4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/public-apis.md`).
+5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
+6. Pat yourself on the back for being an awesome contributor.
+7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
+

airbyte-source-public-apis-0.2.0/airbyte_source_public_apis.egg-info/PKG-INFO

@@ -0,0 +1,70 @@
+Metadata-Version: 2.1
+Name: airbyte-source-public-apis
+Version: 0.2.0
+Summary: Source implementation for Public Apis.
+Author: Airbyte
+Author-email: contact@airbyte.io
+Description-Content-Type: text/markdown
+Requires-Dist: airbyte-cdk
+Provides-Extra: tests
+Requires-Dist: requests-mock~=1.9.3; extra == "tests"
+Requires-Dist: pytest~=6.2; extra == "tests"
+Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
+
+# Public Apis Source
+
+This is the repository for the Public Apis configuration based source connector.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/public-apis).
+
+
+**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/public-apis)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_public_apis/spec.yaml` file.
+Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
+See `integration_tests/sample_config.json` for a sample config file.
+
+**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source public-apis test creds`
+and place them into `secrets/config.json`.
+
+
+
+**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
+```bash
+airbyte-ci connectors --name=source-public-apis build
+```
+
+An image will be built with the tag `airbyte/source-public-apis:dev`.
+
+**Via `docker build`:**
+```bash
+docker build -t airbyte/source-public-apis:dev .
+```
+
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-public-apis:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-public-apis:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-public-apis:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-public-apis:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
+```
+
+You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
+```bash
+airbyte-ci connectors --name=source-public-apis test
+```
+
+Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
+If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
+
+All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
+We split dependencies between two groups, dependencies that are:
+* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
+* required for the testing need to go to `TEST_REQUIREMENTS` list
+
+You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
+1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-public-apis test`
+2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
+3. Make sure the `metadata.yaml` content is up to date.
+4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/public-apis.md`).
+5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
+6. Pat yourself on the back for being an awesome contributor.
+7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.

airbyte-source-public-apis-0.2.0/airbyte_source_public_apis.egg-info/SOURCES.txt

@@ -0,0 +1,24 @@
+README.md
+setup.cfg
+setup.py
+airbyte_source_public_apis.egg-info/PKG-INFO
+airbyte_source_public_apis.egg-info/SOURCES.txt
+airbyte_source_public_apis.egg-info/dependency_links.txt
+airbyte_source_public_apis.egg-info/entry_points.txt
+airbyte_source_public_apis.egg-info/requires.txt
+airbyte_source_public_apis.egg-info/top_level.txt
+integration_tests/__init__.py
+integration_tests/abnormal_state.json
+integration_tests/acceptance.py
+integration_tests/configured_catalog.json
+integration_tests/invalid_config.json
+integration_tests/sample_config.json
+integration_tests/sample_state.json
+source_public_apis/__init__.py
+source_public_apis/components.py
+source_public_apis/manifest.yaml
+source_public_apis/run.py
+source_public_apis/source.py
+source_public_apis/spec.yaml
+source_public_apis/schemas/categories.json
+source_public_apis/schemas/services.json

airbyte-source-public-apis-0.2.0/airbyte_source_public_apis.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

airbyte-source-public-apis-0.2.0/airbyte_source_public_apis.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+source-public-apis = source_public_apis.run:run

airbyte-source-public-apis-0.2.0/airbyte_source_public_apis.egg-info/requires.txt

@@ -0,0 +1,6 @@
+airbyte-cdk
+
+[tests]
+requests-mock~=1.9.3
+pytest~=6.2
+pytest-mock~=3.6.1

airbyte-source-public-apis-0.2.0/airbyte_source_public_apis.egg-info/top_level.txt

@@ -0,0 +1,2 @@
+integration_tests
+source_public_apis

airbyte-source-public-apis-0.2.0/integration_tests/__init__.py

@@ -0,0 +1,3 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#

airbyte-source-public-apis-0.2.0/integration_tests/abnormal_state.json

@@ -0,0 +1,5 @@
+{
+  "todo-stream-name": {
+    "todo-field-name": "todo-abnormal-value"
+  }
+}

airbyte-source-public-apis-0.2.0/integration_tests/acceptance.py

@@ -0,0 +1,16 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#
+
+
+import pytest
+
+pytest_plugins = ("connector_acceptance_test.plugin",)
+
+
+@pytest.fixture(scope="session", autouse=True)
+def connector_setup():
+    """This fixture is a placeholder for external resources that acceptance test might require."""
+    # TODO: setup test dependencies if needed. otherwise remove the TODO comments
+    yield
+    # TODO: clean up test dependencies

airbyte-source-public-apis-0.2.0/integration_tests/configured_catalog.json

@@ -0,0 +1,22 @@
+{
+  "streams": [
+    {
+      "stream": {
+        "name": "services",
+        "json_schema": {},
+        "supported_sync_modes": ["full_refresh"]
+      },
+      "sync_mode": "full_refresh",
+      "destination_sync_mode": "overwrite"
+    },
+    {
+      "stream": {
+        "name": "categories",
+        "json_schema": {},
+        "supported_sync_modes": ["full_refresh"]
+      },
+      "sync_mode": "full_refresh",
+      "destination_sync_mode": "overwrite"
+    }
+  ]
+}

airbyte-source-public-apis-0.2.0/integration_tests/invalid_config.json

@@ -0,0 +1,3 @@
+{
+  "invalid": "config_key"
+}

airbyte-source-public-apis-0.2.0/integration_tests/sample_config.json

@@ -0,0 +1 @@
+{}

airbyte-source-public-apis-0.2.0/integration_tests/sample_state.json

@@ -0,0 +1,5 @@
+{
+  "todo-stream-name": {
+    "todo-field-name": "value"
+  }
+}

airbyte-source-public-apis-0.2.0/setup.cfg

@@ -0,0 +1,68 @@
+[metadata]
+name = airbyte-source-public-apis
+version = 0.2.0
+author = Airbyte
+author_email = contact@airbyte.io
+long_description = # Public Apis Source
+	
+	This is the repository for the Public Apis configuration based source connector.
+	For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/public-apis).
+	
+	
+	**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/public-apis)
+	to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_public_apis/spec.yaml` file.
+	Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
+	See `integration_tests/sample_config.json` for a sample config file.
+	
+	**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source public-apis test creds`
+	and place them into `secrets/config.json`.
+	
+	
+	
+	**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
+	```bash
+	airbyte-ci connectors --name=source-public-apis build
+	```
+	
+	An image will be built with the tag `airbyte/source-public-apis:dev`.
+	
+	**Via `docker build`:**
+	```bash
+	docker build -t airbyte/source-public-apis:dev .
+	```
+	
+	Then run any of the connector commands as follows:
+	```
+	docker run --rm airbyte/source-public-apis:dev spec
+	docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-public-apis:dev check --config /secrets/config.json
+	docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-public-apis:dev discover --config /secrets/config.json
+	docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-public-apis:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
+	```
+	
+	You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
+	```bash
+	airbyte-ci connectors --name=source-public-apis test
+	```
+	
+	Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
+	If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
+	
+	All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
+	We split dependencies between two groups, dependencies that are:
+	* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
+	* required for the testing need to go to `TEST_REQUIREMENTS` list
+	
+	You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
+	1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-public-apis test`
+	2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
+	3. Make sure the `metadata.yaml` content is up to date.
+	4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/public-apis.md`).
+	5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
+	6. Pat yourself on the back for being an awesome contributor.
+	7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
+long_description_content_type = text/markdown
+
+[egg_info]
+tag_build = 
+tag_date = 0
+

airbyte-source-public-apis-0.2.0/setup.py

@@ -0,0 +1,39 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#
+
+
+from setuptools import find_packages, setup
+
+MAIN_REQUIREMENTS = [
+    "airbyte-cdk",
+]
+
+TEST_REQUIREMENTS = ["requests-mock~=1.9.3", "pytest~=6.2", "pytest-mock~=3.6.1"]
+
+setup(
+    entry_points={
+        "console_scripts": [
+            "source-public-apis=source_public_apis.run:run",
+        ],
+    },
+    description="Source implementation for Public Apis.",
+    packages=find_packages(),
+    install_requires=MAIN_REQUIREMENTS,
+    package_data={
+        "": [
+            # Include yaml files in the package (if any)
+            "*.yml",
+            "*.yaml",
+            # Include all json files in the package, up to 4 levels deep
+            "*.json",
+            "*/*.json",
+            "*/*/*.json",
+            "*/*/*/*.json",
+            "*/*/*/*/*.json",
+        ]
+    },
+    extras_require={
+        "tests": TEST_REQUIREMENTS,
+    },
+)

airbyte-source-public-apis-0.2.0/source_public_apis/__init__.py

@@ -0,0 +1,8 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#
+
+
+from .source import SourcePublicApis
+
+__all__ = ["SourcePublicApis"]

airbyte-source-public-apis-0.2.0/source_public_apis/components.py

@@ -0,0 +1,14 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#
+
+from typing import Any, List, Mapping
+
+import requests
+from airbyte_cdk.sources.declarative.extractors.record_extractor import RecordExtractor
+
+
+class CustomExtractor(RecordExtractor):
+    def extract_records(self, response: requests.Response, **kwargs) -> List[Mapping[str, Any]]:
+
+        return [{"name": cat} for cat in response.json()["categories"]]

airbyte-source-public-apis-0.2.0/source_public_apis/manifest.yaml

@@ -0,0 +1,60 @@
+version: "0.29.0"
+
+definitions:
+  selector:
+    type: RecordSelector
+    extractor:
+      type: DpathExtractor
+      field_path: ["entries"]
+
+  selector_categories:
+    type: RecordSelector
+    extractor:
+      type: CustomRecordExtractor
+      class_name: source_public_apis.components.CustomExtractor
+
+  requester:
+    type: HttpRequester
+    url_base: "https://api.publicapis.org/"
+    http_method: "GET"
+    authenticator:
+      type: NoAuth
+
+  retriever:
+    type: SimpleRetriever
+    record_selector:
+      $ref: "#/definitions/selector"
+    paginator:
+      type: NoPagination
+    requester:
+      $ref: "#/definitions/requester"
+
+  base_stream:
+    type: DeclarativeStream
+    retriever:
+      $ref: "#/definitions/retriever"
+
+  categories_stream:
+    $ref: "#/definitions/base_stream"
+    retriever:
+      $ref: "#/definitions/retriever"
+      record_selector:
+        $ref: "#/definitions/selector_categories"
+    $parameters:
+      name: "categories"
+      path: "/categories"
+
+  services_stream:
+    $ref: "#/definitions/base_stream"
+    $parameters:
+      name: "services"
+      path: "/entries"
+
+streams:
+  - "#/definitions/categories_stream"
+  - "#/definitions/services_stream"
+
+check:
+  type: CheckStream
+  stream_names:
+    - "categories"

airbyte-source-public-apis-0.2.0/source_public_apis/run.py

@@ -0,0 +1,14 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#
+
+
+import sys
+
+from airbyte_cdk.entrypoint import launch
+from source_public_apis import SourcePublicApis
+
+
+def run():
+    source = SourcePublicApis()
+    launch(source, sys.argv[1:])

airbyte-source-public-apis-0.2.0/source_public_apis/schemas/categories.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "additionalProperties": true,
+  "properties": {
+    "name": {
+      "type": ["null", "string"]
+    }
+  }
+}

airbyte-source-public-apis-0.2.0/source_public_apis/schemas/services.json

@@ -0,0 +1,28 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "additionalProperties": true,
+  "properties": {
+    "API": {
+      "type": ["null", "string"]
+    },
+    "Description": {
+      "type": ["null", "string"]
+    },
+    "Auth": {
+      "type": ["null", "string"]
+    },
+    "HTTPS": {
+      "type": ["null", "boolean"]
+    },
+    "Cors": {
+      "type": ["null", "string"]
+    },
+    "Link": {
+      "type": ["null", "string"]
+    },
+    "Category": {
+      "type": ["null", "string"]
+    }
+  }
+}

airbyte-source-public-apis-0.2.0/source_public_apis/source.py

@@ -0,0 +1,18 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#
+
+from airbyte_cdk.sources.declarative.yaml_declarative_source import YamlDeclarativeSource
+
+"""
+This file provides the necessary constructs to interpret a provided declarative YAML configuration file into
+source connector.
+
+WARNING: Do not modify this file.
+"""
+
+
+# Declarative Source
+class SourcePublicApis(YamlDeclarativeSource):
+    def __init__(self):
+        super().__init__(**{"path_to_yaml": "manifest.yaml"})

airbyte-source-public-apis-0.2.0/source_public_apis/spec.yaml

@@ -0,0 +1,7 @@
+documentationUrl: https://docs.airbyte.com/integrations/sources/public-apis
+connectionSpecification:
+  $schema: http://json-schema.org/draft-07/schema#
+  title: Public Apis Spec
+  type: object
+  additionalProperties: true
+  properties: {}