Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
airbyte-source-wikipedia-pageviews
Advanced tools
This is the repository for the Wikipedia Pageviews configuration based source connector. For information about how to use this connector within Airbyte, see the documentation.
^3.9
)^1.7
) - installation instructions hereFrom this connector directory, run:
poetry install --with dev
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 spec
inside source_wikipedia_pageviews/manifest.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.
poetry run source-wikipedia-pageviews spec
poetry run source-wikipedia-pageviews check --config secrets/config.json
poetry run source-wikipedia-pageviews discover --config secrets/config.json
poetry run source-wikipedia-pageviews read --config secrets/config.json --catalog integration_tests/configured_catalog.json
To run tests locally, from the connector directory run:
poetry run pytest tests
airbyte-ci
airbyte-ci connectors --name=source-wikipedia-pageviews build
An image will be available on your host with the tag airbyte/source-wikipedia-pageviews:dev
.
Then run any of the connector commands as follows:
docker run --rm airbyte/source-wikipedia-pageviews:dev spec
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-wikipedia-pageviews:dev check --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-wikipedia-pageviews:dev discover --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-wikipedia-pageviews: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-wikipedia-pageviews test
Customize acceptance-test-config.yml
file to configure acceptance 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 be managed via Poetry. To add a new dependency, run:
poetry add <package-name>
Please commit the changes to pyproject.toml
and poetry.lock
files.
You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
airbyte-ci connectors --name=source-wikipedia-pageviews test
dockerImageTag
value in in metadata.yaml
version
value in pyproject.toml
metadata.yaml
content is up to date.docs/integrations/sources/wikipedia-pageviews.md
).FAQs
Source implementation for wikipedia-pageviews.
We found that airbyte-source-wikipedia-pageviews demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.