From 747bf52f10ac65017e5a41f4a93fa34ce7484674 Mon Sep 17 00:00:00 2001 From: fivetran-abdulsalam Date: Fri, 26 Jul 2024 13:23:42 +0530 Subject: [PATCH] added single tester docker repo in doc --- tools/connector-tester/README.md | 5 +---- tools/destination-tester/README.md | 5 +---- 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/tools/connector-tester/README.md b/tools/connector-tester/README.md index d4fb2da..ad0337a 100644 --- a/tools/connector-tester/README.md +++ b/tools/connector-tester/README.md @@ -11,7 +11,7 @@ 2. Run a container using the image with the following command. Make sure to map a local directory for storing files that the tool generates by replacing `` in the command, and replace with the version of the image you pulled. ``` -docker run --mount type=bind,source=,target=/data -a STDIN -a STDOUT -a STDERR -it -e GRPC_HOSTNAME=host.docker.internal --network=host fivetrandocker/sdk-connector-tester: +docker run --mount type=bind,source=,target=/data -a STDIN -a STDOUT -a STDERR -it -e GRPC_HOSTNAME=host.docker.internal --network=host fivetrandocker/fivetran-sdk-tester: --tester-type source --port ``` 3. Once the sync is done running, it will persist the records in a `warehouse.db` database file. This is an instance of [DuckDB](https://duckdb.org/) database. You can connect to it to validate the results of your sync using [DuckDB CLI](https://duckdb.org/docs/api/cli) or [DBeaver](https://duckdb.org/docs/guides/sql_editors/dbeaver) @@ -26,8 +26,5 @@ docker start -i The tester supports the following optional CLI arguments to alter its default behavior. You can append these options to the end of the docker run command provided in step 2 of [How To Run](https://github.com/fivetran/fivetran_sdk/blob/main/tools/connector-tester/README.md#how-to-run) section above. -#### --port -This option tells the tester to use a different port than the default 50051. - #### --destination-schema With this option, you can alter the schema name used in the destination from the default `default_schema`. diff --git a/tools/destination-tester/README.md b/tools/destination-tester/README.md index 54c1e3f..78b8e6f 100644 --- a/tools/destination-tester/README.md +++ b/tools/destination-tester/README.md @@ -10,7 +10,7 @@ 2. Run a container using the image with the following command. Make sure to map a local directory for the tool by replacing `` placeholders in the command, and replace `` with the version of the image you pulled. ``` -docker run --mount type=bind,source=,target=/data -a STDIN -a STDOUT -a STDERR -it -e WORKING_DIR= -e GRPC_HOSTNAME=host.docker.internal --network=host fivetrandocker/sdk-destination-tester: +docker run --mount type=bind,source=,target=/data -a STDIN -a STDOUT -a STDERR -it -e WORKING_DIR= -e GRPC_HOSTNAME=host.docker.internal --network=host fivetrandocker/fivetran-sdk-tester: --tester-type destination --port ``` 3. To rerun the container from step #2, use the following command: @@ -145,9 +145,6 @@ Here is an example input file named `input_1.json`: The tester supports the following optional CLI arguments to alter its default behavior. You can append these options to the end of the `docker run` command provided in step 2 of [How To Run](https://github.com/fivetran/fivetran_sdk/tree/main/tools/destination-tester#how-to-run) section above. -#### --port -This option tells the tester to use a different port than the default 50052. - #### --plain-text This option disables encryption and compression of batch files for debugging purposes.