tap-googlesearch
installation
Install using pip:
pip install tap-googlesearch
example
tap-googlesearch -c config.json > records.ndjson
and test using the singer-check-tap by installing the singer-tools as well:
pipenv install tap-googlesearch singer-tools
pipenv run tap-googlesearch -c example_config.json | pipenv run singer-check-tap
config
Below is an example of a valid config.json for this tap. There's an optional start_date field that will default to 24 weeks in the past if not set.
{
"oauth2_credentials_file": "<fully qualified path to the OAuth2.0 credentials file>",
"dimensions": ["page", "query"],
"start_date": "2018-05-23",
"site_urls": ["<optional list of site_urls to include (defaults to all)>"]
}
Metadata
Release files for tap-googlesearch 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tap-googlesearch-0.2.tar.gz | 4.9 kB | Without provenance | Details for tap-googlesearch-0.2.tar.gz |
Release files / tap-googlesearch-0.2.tar.gz
| Download URL | tap-googlesearch-0.2.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e83454f58131e324c6849d95e6ef3e69b8f704382a3902c57fd624df3546a54
|
|
BLAKE2b-256 checksum How to use checksums |
5cc8817e34deef5af0c5dbc4530e548844917f2f78590764ebd091dd76efe7c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.42.0 CPython/3.7.6
|
Security for tap-googlesearch 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.