🎉 Source Chargebee: enable high strictness

airbyte-config/init/src/main/resources/seed/source_definitions.yaml

@@ -242,6 +242,9 @@
   icon: chargebee.svg
   sourceType: api
   releaseStage: generally_available
+  allowedHosts:
+    hosts:
+      - "*.chargebee.com"
 - name: Chargify
   sourceDefinitionId: 9b2d3607-7222-4709-9fa2-c2abdebbdd88
   dockerRepository: airbyte/source-chargify

airbyte-integrations/connectors/source-chargebee/Dockerfile

@@ -13,5 +13,5 @@ RUN pip install .
 
 ENTRYPOINT ["python", "/airbyte/integration_code/main.py"]
 
-LABEL io.airbyte.version=0.1.16
+LABEL io.airbyte.version=0.2.1
 LABEL io.airbyte.name=airbyte/source-chargebee

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

@@ -97,7 +97,8 @@ Customize `acceptance-test-config.yml` file to configure tests. See [Connector A
 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.
 To run your integration tests with acceptance tests, from the connector root, run
 ```
-python -m pytest integration_tests -p integration_tests.acceptance
+docker build . --no-cache -t airbyte/source-chargebee:dev \
+&& python -m pytest -p connector_acceptance_test.plugin
 ```
 To run your integration tests with docker
 

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

@@ -1,31 +1,38 @@
 # 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-chargebee:dev
-tests:
+test_strictness_level: high
+acceptance_tests:
   spec:
-    - spec_path: "source_chargebee/spec.json"
+    tests:
+      - spec_path: "source_chargebee/spec.json"
   connection:
-    - config_path: "secrets/config.json"
-      status: "succeed"
-    - config_path: "integration_tests/invalid_config.json"
-      status: "failed"
+    tests:
+      - config_path: "secrets/config.json"
+        status: "succeed"
+      - config_path: "integration_tests/invalid_config.json"
+        status: "failed"
   discovery:
-    - config_path: "secrets/config.json"
-      backward_compatibility_tests_config:
-        disable_for_version: "0.1.12"
+    tests:
+      - config_path: "secrets/config.json"
+        # Got rid of unnecessary `enum` from schema, causing the invalid values validation errors.
+        # TODO: please remove this block during next updates.
+        backward_compatibility_tests_config:
+          disable_for_version: "0.2.0"
   basic_read:
-    - config_path: "secrets/config.json"
-      configured_catalog_path: "integration_tests/product_catalog_v2_configured_catalog.json"
-      # I was unable to create orders using API and I didn’t find a way to create orders
-      # through UI, so that’s why `order` stream is empty.
-      empty_streams:
-        - order
-  incremental:
-    - config_path: "secrets/config.json"
-      configured_catalog_path: "integration_tests/product_catalog_v2_configured_catalog.json"
-      future_state_path: "integration_tests/future_state.json"
-      cursor_paths:
-        attached_item: [ "cbdemo_standard", "updated_at" ]
+    tests:
+      - config_path: "secrets/config.json"
+        expect_records:
+          path: "integration_tests/expected_records.jsonl"
   full_refresh:
-    - config_path: "secrets/config.json"
-      configured_catalog_path: "integration_tests/product_catalog_v2_configured_catalog.json"
+    tests:
+      - config_path: "secrets/config.json"
+        configured_catalog_path: "integration_tests/configured_catalog.json"
+  incremental:
+    tests:
+      - config_path: "secrets/config.json"
+        configured_catalog_path: "integration_tests/configured_catalog.json"
+        future_state:
+          future_state_path: "integration_tests/future_state.json"
+        cursor_paths:
+          attached_item: [ "cbdemo_premium", "updated_at" ]