airbyte-source-lemlist


Nameairbyte-source-lemlist JSON
Version 0.2.14 PyPI version JSON
download
home_pagehttps://airbyte.com
SummarySource implementation for Lemlist.
upload_time2024-08-18 02:43:41
maintainerNone
docs_urlNone
authorAirbyte
requires_python<3.12,>=3.9
licenseMIT
keywords
VCS
bugtrack_url
requirements No requirements were recorded.
Travis-CI No Travis.
coveralls test coverage No coveralls.
            # Lemlist Source

This is the repository for the Lemlist configuration based source connector.
For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/lemlist).

## Local development

#### Create credentials

**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/lemlist)
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_lemlist/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 lemlist test creds`
and place them into `secrets/config.json`.

### Locally running the connector docker image

#### Build

**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**

```bash
airbyte-ci connectors --name=source-lemlist build
```

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

**Via `docker build`:**

```bash
docker build -t airbyte/source-lemlist:dev .
```

#### Run

Then run any of the connector commands as follows:

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

## Testing

You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):

```bash
airbyte-ci connectors --name=source-lemlist test
```

### Customizing acceptance Tests

Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) 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.

## Dependency Management

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

### Publishing a new version of the connector

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-lemlist test`
2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#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/lemlist.md`).
5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
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.

            

Raw data

            {
    "_id": null,
    "home_page": "https://airbyte.com",
    "name": "airbyte-source-lemlist",
    "maintainer": null,
    "docs_url": null,
    "requires_python": "<3.12,>=3.9",
    "maintainer_email": null,
    "keywords": null,
    "author": "Airbyte",
    "author_email": "contact@airbyte.io",
    "download_url": "https://files.pythonhosted.org/packages/5a/fa/f33a902f268dad7042c2d81736e81ae8a90bd46f078afc80fd01bb005006/airbyte_source_lemlist-0.2.14.tar.gz",
    "platform": null,
    "description": "# Lemlist Source\n\nThis is the repository for the Lemlist configuration based source connector.\nFor information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/lemlist).\n\n## Local development\n\n#### Create credentials\n\n**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/lemlist)\nto generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_lemlist/spec.yaml` file.\nNote that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.\nSee `integration_tests/sample_config.json` for a sample config file.\n\n**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source lemlist test creds`\nand place them into `secrets/config.json`.\n\n### Locally running the connector docker image\n\n#### Build\n\n**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**\n\n```bash\nairbyte-ci connectors --name=source-lemlist build\n```\n\nAn image will be built with the tag `airbyte/source-lemlist:dev`.\n\n**Via `docker build`:**\n\n```bash\ndocker build -t airbyte/source-lemlist:dev .\n```\n\n#### Run\n\nThen run any of the connector commands as follows:\n\n```\ndocker run --rm airbyte/source-lemlist:dev spec\ndocker run --rm -v $(pwd)/secrets:/secrets airbyte/source-lemlist:dev check --config /secrets/config.json\ndocker run --rm -v $(pwd)/secrets:/secrets airbyte/source-lemlist:dev discover --config /secrets/config.json\ndocker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-lemlist:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json\n```\n\n## Testing\n\nYou can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):\n\n```bash\nairbyte-ci connectors --name=source-lemlist test\n```\n\n### Customizing acceptance Tests\n\nCustomize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.\nIf 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.\n\n## Dependency Management\n\nAll 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.\nWe split dependencies between two groups, dependencies that are:\n\n- required for your connector to work need to go to `MAIN_REQUIREMENTS` list.\n- required for the testing need to go to `TEST_REQUIREMENTS` list\n\n### Publishing a new version of the connector\n\nYou've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?\n\n1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-lemlist test`\n2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).\n3. Make sure the `metadata.yaml` content is up to date.\n4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/lemlist.md`).\n5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).\n6. Pat yourself on the back for being an awesome contributor.\n7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.\n",
    "bugtrack_url": null,
    "license": "MIT",
    "summary": "Source implementation for Lemlist.",
    "version": "0.2.14",
    "project_urls": {
        "Documentation": "https://docs.airbyte.com/integrations/sources/lemlist",
        "Homepage": "https://airbyte.com",
        "Repository": "https://github.com/airbytehq/airbyte"
    },
    "split_keywords": [],
    "urls": [
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "5adaae3f71926ec3770b8435da43eb4943a734b006cc6fe64b6698951b86d508",
                "md5": "21414f3ebcdd353a5deb47f3543ab10b",
                "sha256": "1ba88f9791f31d4d34617fffe49067a465f08a7fc1b971ef4f5ad83310fdb557"
            },
            "downloads": -1,
            "filename": "airbyte_source_lemlist-0.2.14-py3-none-any.whl",
            "has_sig": false,
            "md5_digest": "21414f3ebcdd353a5deb47f3543ab10b",
            "packagetype": "bdist_wheel",
            "python_version": "py3",
            "requires_python": "<3.12,>=3.9",
            "size": 5517,
            "upload_time": "2024-08-18T02:43:40",
            "upload_time_iso_8601": "2024-08-18T02:43:40.524609Z",
            "url": "https://files.pythonhosted.org/packages/5a/da/ae3f71926ec3770b8435da43eb4943a734b006cc6fe64b6698951b86d508/airbyte_source_lemlist-0.2.14-py3-none-any.whl",
            "yanked": false,
            "yanked_reason": null
        },
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "5afaf33a902f268dad7042c2d81736e81ae8a90bd46f078afc80fd01bb005006",
                "md5": "fb3dce0e5dd02a90e5c4cb1a24db4379",
                "sha256": "caa0fddabdd1268b7374db1c6c254e352d9f0f0e80fc48c6e172246d7821c7d6"
            },
            "downloads": -1,
            "filename": "airbyte_source_lemlist-0.2.14.tar.gz",
            "has_sig": false,
            "md5_digest": "fb3dce0e5dd02a90e5c4cb1a24db4379",
            "packagetype": "sdist",
            "python_version": "source",
            "requires_python": "<3.12,>=3.9",
            "size": 4308,
            "upload_time": "2024-08-18T02:43:41",
            "upload_time_iso_8601": "2024-08-18T02:43:41.394768Z",
            "url": "https://files.pythonhosted.org/packages/5a/fa/f33a902f268dad7042c2d81736e81ae8a90bd46f078afc80fd01bb005006/airbyte_source_lemlist-0.2.14.tar.gz",
            "yanked": false,
            "yanked_reason": null
        }
    ],
    "upload_time": "2024-08-18 02:43:41",
    "github": true,
    "gitlab": false,
    "bitbucket": false,
    "codeberg": false,
    "github_user": "airbytehq",
    "github_project": "airbyte",
    "travis_ci": false,
    "coveralls": false,
    "github_actions": true,
    "lcname": "airbyte-source-lemlist"
}
        
Elapsed time: 0.31278s