|
| 1 | +# Google Search Console Source |
| 2 | + |
| 3 | +This is the repository for the Google Search Console source connector, written in Python. |
| 4 | +For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/google-search-console). |
| 5 | + |
| 6 | +## Local development |
| 7 | + |
| 8 | +### Prerequisites |
| 9 | +**To iterate on this connector, make sure to complete this prerequisites section.** |
| 10 | + |
| 11 | +#### Minimum Python version required `= 3.7.0` |
| 12 | + |
| 13 | +#### Build & Activate Virtual Environment and install dependencies |
| 14 | +From this connector directory, create a virtual environment: |
| 15 | +``` |
| 16 | +python -m venv .venv |
| 17 | +``` |
| 18 | + |
| 19 | +This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your |
| 20 | +development environment of choice. To activate it from the terminal, run: |
| 21 | +``` |
| 22 | +source .venv/bin/activate |
| 23 | +pip install -r requirements.txt |
| 24 | +``` |
| 25 | +If you are in an IDE, follow your IDE's instructions to activate the virtualenv. |
| 26 | + |
| 27 | +Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is |
| 28 | +used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`. |
| 29 | +If this is mumbo jumbo to you, don't worry about it, just put your deps in `setup.py` but install using `pip install -r requirements.txt` and everything |
| 30 | +should work as you expect. |
| 31 | + |
| 32 | +#### Building via Gradle |
| 33 | +From the Airbyte repository root, run: |
| 34 | +``` |
| 35 | +./gradlew :airbyte-integrations:connectors:source-google-search-console:build |
| 36 | +``` |
| 37 | + |
| 38 | +#### Create credentials |
| 39 | +**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/google-search-console) |
| 40 | +to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_google_search_console/spec.json` file. |
| 41 | +Note that the `secrets` directory is gitignored by default, so there is no danger of accidentally checking in sensitive information. |
| 42 | +See `integration_tests/sample_config.json` for a sample config file. |
| 43 | + |
| 44 | +**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source google-search-console test creds` |
| 45 | +and place them into `secrets/config.json`. |
| 46 | + |
| 47 | +### Locally running the connector |
| 48 | +``` |
| 49 | +python main.py spec |
| 50 | +python main.py check --config secrets/config.json |
| 51 | +python main.py discover --config secrets/config.json |
| 52 | +python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json |
| 53 | +``` |
| 54 | + |
| 55 | +### Locally running the connector docker image |
| 56 | + |
| 57 | +#### Build |
| 58 | +First, make sure you build the latest Docker image: |
| 59 | +``` |
| 60 | +docker build . -t airbyte/source-google-search-console:dev |
| 61 | +``` |
| 62 | + |
| 63 | +You can also build the connector image via Gradle: |
| 64 | +``` |
| 65 | +./gradlew :airbyte-integrations:connectors:source-google-search-console:airbyteDocker |
| 66 | +``` |
| 67 | +When building via Gradle, the docker image name and tag, respectively, are the values of the `io.airbyte.name` and `io.airbyte.version` `LABEL`s in |
| 68 | +the Dockerfile. |
| 69 | + |
| 70 | +#### Run |
| 71 | +Then run any of the connector commands as follows: |
| 72 | +``` |
| 73 | +docker run --rm airbyte/source-google-search-console:dev spec |
| 74 | +docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-search-console:dev check --config /secrets/config.json |
| 75 | +docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-search-console:dev discover --config /secrets/config.json |
| 76 | +docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-google-search-console:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json |
| 77 | +``` |
| 78 | +## Testing |
| 79 | + Make sure to familiarize yourself with [pytest test discovery](https://docs.pytest.org/en/latest/goodpractices.html#test-discovery) to know how your test files and methods should be named. |
| 80 | +First install test dependencies into your virtual environment: |
| 81 | +``` |
| 82 | +pip install .[tests] |
| 83 | +``` |
| 84 | +### Unit Tests |
| 85 | +To run unit tests locally, from the connector directory run: |
| 86 | +``` |
| 87 | +python -m pytest unit_tests |
| 88 | +``` |
| 89 | + |
| 90 | +### Integration Tests |
| 91 | +There are two types of integration tests: Acceptance Tests (Airbyte's test suite for all source connectors) and custom integration tests (which are specific to this connector). |
| 92 | +#### Custom Integration tests |
| 93 | +Place custom tests inside `integration_tests/` folder, then, from the connector root, run |
| 94 | +``` |
| 95 | +python -m pytest integration_tests |
| 96 | +``` |
| 97 | +#### Acceptance Tests |
| 98 | +Customize `acceptance-test-config.yml` file to configure tests. See [Source Acceptance Tests](source-acceptance-tests.md) for more information. |
| 99 | +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. |
| 100 | +To run your integration tests with acceptance tests, from the connector root, run |
| 101 | +``` |
| 102 | +python -m pytest integration_tests -p integration_tests.acceptance |
| 103 | +``` |
| 104 | +To run your integration tests with docker |
| 105 | + |
| 106 | +### Using gradle to run tests |
| 107 | +All commands should be run from airbyte project root. |
| 108 | +To run unit tests: |
| 109 | +``` |
| 110 | +./gradlew :airbyte-integrations:connectors:source-google-search-console:unitTest |
| 111 | +``` |
| 112 | +To run acceptance and custom integration tests: |
| 113 | +``` |
| 114 | +./gradlew :airbyte-integrations:connectors:source-google-search-console:integrationTest |
| 115 | +``` |
| 116 | + |
| 117 | +## Dependency Management |
| 118 | +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. |
| 119 | +We split dependencies between two groups, dependencies that are: |
| 120 | +* required for your connector to work need to go to `MAIN_REQUIREMENTS` list. |
| 121 | +* required for the testing need to go to `TEST_REQUIREMENTS` list |
| 122 | + |
| 123 | +### Publishing a new version of the connector |
| 124 | +You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what? |
| 125 | +1. Make sure your changes are passing unit and integration tests. |
| 126 | +1. Bump the connector version in `Dockerfile` -- just increment the value of the `LABEL io.airbyte.version` appropriately (we use [SemVer](https://semver.org/)). |
| 127 | +1. Create a Pull Request. |
| 128 | +1. Pat yourself on the back for being an awesome contributor. |
| 129 | +1. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master. |
0 commit comments