Skip to main content

Source implementation for Woocommerce.

Project description

Woocommerce Source

This is the repository for the Woocommerce configuration based source connector. For information about how to use this connector within Airbyte, see the documentation.

If you are a community contributor, follow the instructions in the documentation to generate the necessary credentials. Then create a file secrets/config.json conforming to the source_woocommerce/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 woocommerce test creds and place them into secrets/config.json.

Via airbyte-ci (recommended):

airbyte-ci connectors --name=source-woocommerce build

An image will be built with the tag airbyte/source-woocommerce:dev.

Via docker build:

docker build -t airbyte/source-woocommerce:dev .

Then run any of the connector commands as follows:

docker run --rm airbyte/source-woocommerce:dev spec
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-woocommerce:dev check --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-woocommerce:dev discover --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-woocommerce:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json

You can run our full test suite locally using airbyte-ci:

airbyte-ci connectors --name=source-woocommerce test

Customize acceptance-test-config.yml file to configure tests. See Connector Acceptance Tests 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-woocommerce test
  2. Bump the connector version in metadata.yaml: increment the dockerImageTag value. Please follow 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/woocommerce.md).
  5. Create a Pull Request: use our PR naming conventions.
  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.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

airbyte-source-woocommerce-0.2.3.tar.gz (12.0 kB view details)

Uploaded Source

Built Distribution

File details

Details for the file airbyte-source-woocommerce-0.2.3.tar.gz.

File metadata

File hashes

Hashes for airbyte-source-woocommerce-0.2.3.tar.gz
Algorithm Hash digest
SHA256 e73b6a99123888e63b4e9661a2334e544f72447e7edbb32c816f5a432cfdf684
MD5 00818aff869c4b9d2555bbd78e38f260
BLAKE2b-256 995552fbc8ba909a896d607e4acc4e07de4ad99a266df0116af8cbe99e8add05

See more details on using hashes here.

File details

Details for the file airbyte_source_woocommerce-0.2.3-py3-none-any.whl.

File metadata

File hashes

Hashes for airbyte_source_woocommerce-0.2.3-py3-none-any.whl
Algorithm Hash digest
SHA256 06aa25e389a44bdf996750d7523c178064e8429191cd4ee7e735a90a3cffd92c
MD5 fa7aa1946875e3bd98b6304043315240
BLAKE2b-256 1f65f0082730ca1f7648efcae7a20bb40ad4429fa3cc9bc91e184764355d1e42

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page