source-freightview contribution from parthiv11

airbyte-integrations/connectors/source-freightview/README.md

@@ -0,0 +1,33 @@
+# Freightview
+This directory contains the manifest-only connector for `source-freightview`.
+
+An **Airbyte connector for Freightview** enables seamless data integration by extracting and syncing shipping data from Freightview to your target data warehouses or applications. This connector automates the retrieval of essential shipping details, such as quotes, tracking, and shipment reports, allowing businesses to efficiently analyze and manage logistics operations in a centralized system.
+
+## Usage
+There are multiple ways to use this connector:
+- You can use this connector as any other connector in Airbyte Marketplace.
+- You can load this connector in `pyairbyte` using `get_source`!
+- You can open this connector in Connector Builder, edit it, and publish to your workspaces.
+
+Please refer to the manifest-only connector documentation for more details.
+
+## Local Development
+We recommend you use the Connector Builder to edit this connector.
+
+But, if you want to develop this connector locally, you can use the following steps.
+
+### Environment Setup
+You will need `airbyte-ci` installed. You can find the documentation [here](airbyte-ci).
+
+### Build
+This will create a dev image (`source-freightview:dev`) that you can use to test the connector locally.
+```bash
+airbyte-ci connectors --name=source-freightview build
+```
+
+### Test
+This will run the acceptance tests for the connector.
+```bash
+airbyte-ci connectors --name=source-freightview test
+```
+

airbyte-integrations/connectors/source-freightview/acceptance-test-config.yml

@@ -0,0 +1,17 @@
+# See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference)
+# for more information about how to configure these tests
+connector_image: airbyte/source-freightview:dev
+acceptance_tests:
+  spec:
+    tests:
+      - spec_path: "manifest.yaml"
+  connection:
+    bypass_reason: "This is a builder contribution, and we do not have secrets at this time"
+  discovery:
+    bypass_reason: "This is a builder contribution, and we do not have secrets at this time"
+  basic_read:
+    bypass_reason: "This is a builder contribution, and we do not have secrets at this time"
+  incremental:
+    bypass_reason: "This is a builder contribution, and we do not have secrets at this time"
+  full_refresh:
+    bypass_reason: "This is a builder contribution, and we do not have secrets at this time"