connector-py


Nameconnector-py JSON
Version 3.2.0 PyPI version JSON
download
home_pageNone
SummaryAn Abstract Tool to Perform Actions on Integrations
upload_time2024-10-03 20:23:23
maintainerNone
docs_urlNone
authorNone
requires_python>=3.10
license Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2024 Lumos App, Inc. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
keywords integrations
VCS
bugtrack_url
requirements No requirements were recorded.
Travis-CI No Travis.
coveralls test coverage No coveralls.
            # Lumos Connectors

[![PyPI - Version](https://img.shields.io/pypi/v/connector-py.svg)](https://pypi.org/project/connector-py)
[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/connector-py.svg)](https://pypi.org/project/connector-py)

-----

## Table of Contents

- [Installation](#installation)
- [Usage](#usage)
- [Error Handling](#error-handling)
- [Scaffold](#scaffold)
- [Unasync](#unasync)
- [FastAPI](#fastapi)
- [Tips](#tips)
- [License](#license)

## Installation

```console
pip install connector-py
```

## Usage

The package can be used in three ways:
1. A CLI to scaffold a custom connector with its own CLI to call commands
2. A library to create a custom connector
3. A library to convert your custom connector code to a FastAPI HTTP server

To get started, run `connector --help`

An example of running a command that accepts arguments
in an integration connector called `mock-connector`:

```shell
mock-connector info --json '{"a": 1}'
```

### Connector implementation
All new connectors should be based on the `connector.integration.Integration` class. The new approach doesn't define capabilities by inheriting from connector interface (called `LumosCommandMixin`) but injects capability implementations into an instance of `Integration` class. This allows us to:
- typecheck the implementations
- partially implemented connectors
- check that implementation accept expected arguments and return expected response
- have connector specific arguments

```python
import httpx
from connector.capability import CapabilityName
from connector.errors import HTTPHandler
from connector.integration import Integration
from connector.serializers.request import (
    BasicCredentials,
    ListAccountsRequest,
    Request,
)
from connector.serializers.response import (
    ListAccountsResponse,
    Response,
)

integration = Integration(
    app_id="app_id",
    auth=BasicCredentials,
    exception_handlers=[
        (httpx.HTTPStatusError, HTTPHandler, None),
    ],
    handle_errors=True,
)


@integration.register_capability(CapabilityName.LIST_ACCOUNTS)
async def list_accounts(request: Request[ListAccountsRequest, None]) -> Response[ListAccountsResponse]:
    # do whatever is needed to get accounts
    return Response[ListAccountsResponse](
        response=ListAccountsResponse(
            accounts=accounts,
        ),
        raw_data=raw_data if request.include_raw_data else None,
        ...
    )
```

#### Converting LumosCommandMixin-based integrations
- if you don't need to sync, drop `sync_/` folder; otherwise drop `async_/`
- in your connector implementation, create instance of `Integration` class, fill-in `app_id`, `exception_handlers` and `auth`
- all methods that implement capabilities have to be decorated with `integration.register_capability(name=CapabilityName.<pick-correct-name>)`
- if you don't need any extra arguments for capability parameters (besides auth and pagination, which are now part of request), remove them and use the standard way provided with `connector.serializers.request.Request` class
- make all tests sync as the `dispatch` method is synchronous and it start the event loop itself
- you're done

### Error Handling

Error handling is facilitated through an exception handler decorator.
See `connector/async_/exception_handler.py` and `connector/errors.py`.

An exception handler can be attached to the connector library as follows:

```python
from httpx import HTTPStatusError
from connector.errors import HTTPHandler
from connector.async_exception_handler import connector_handler

integration = Integration(
    ...,
    exception_handlers=[
        (HTTPStatusError, HTTPHandler, None),
    ],
    handle_errors=True,
)
```

The decorator accepts a list of tuples of three. First tuple argument is the exception you would like to be catching, second is the handler (default or implemented on your own) and third is a specific error code that you would like to associate with this handler.

By default it is recommended to make use of the default HTTPHandler which will handle `raise_for_status()` for you and properly error code it. For more complex errors it is recommended to subclass the ExceptionHandler (in `connector/errors.py`) and craft your own handler.

#### Making your own handler

To setup your own handler, you can extend the abstract ExceptionHandler class:

```python
from connector.errors import ExceptionHandler, ErrorCodes
from connector.serializers.lumos import EncounteredErrorResponse
from connector.serializers.response import Response

class CustomHandler(ExceptionHandler):
    @staticmethod
    def handle(
        e: Exception,
        original_func: t.Any,
        response: Response[EncounteredErrorResponse],
        error_code: str | ErrorCodes | None = None,
    ) -> Response[EncounteredErrorResponse]:
        # Perform any custom logic, another call, modify the response, etc.
        response.error.error_code = "custom_error_code"
        return response
```

#### Raising an exception

Among this, there is a custom exception class available as well as a default list of error codes:

```python
from connector.errors import ConnectorError, ErrorCodes

def some_method(self, args):
    raise ConnectorError("Received wrong data, x: y", ErrorCodes.BAD_REQUEST)
```

It is preferred to raise any manually raisable exception with this class. A connector can implement its own error codes list, which should be properly documented.

### Response

Error codes are by default prefixed with the app_id of the connector that has raised the exception. In your implementation you don't need to worry about this and can only focus on the second and optionally third level of the error code.

An example response when handled this way:

```json
// BAD_REQUEST error from github connector
{"error":{"message":"Some message","status_code":400,"error_code":"github.bad_request","raised_by":"HTTPStatusError","raised_in":"github.sync_.lumos:validate_credentials"}, "response": null, "raw_data": null}
```

### Scaffold

To scaffold a custom connector, run `connector scaffold --help`

To scaffold the mock-connector, run
`connector scaffold mock-connector "projects/connectors/python/mock-connector"`

### Unasync

*Unasync will be removed when all connectors are migrated to `Integration` class approach.*

When developing this package, start off creating async functions and then
convert them to sync functions using `unasync`.

```console
connector hacking unasync
```

### FastAPI

To convert your custom connector to a FastAPI HTTP server, run `connector hacking http-server`

## Tips

#### The library I want to use is synchronous only

You can use a package called `asgiref`. This package converts I/O bound synchronous
calls into asyncio non-blocking calls. First, add asgiref to your dependencies list
in `pyproject.toml`. Then, in your async code, use `asgiref.sync_to_async` to convert
synchronous calls to asynchronous calls.

```python
from asgiref.sync import sync_to_async
import requests

async def async_get_data():
    response = await sync_to_async(requests.get)("url")
```

## License

`connector` is distributed under the terms of the [Apache 2.0](./LICENSE.txt) license.

            

Raw data

            {
    "_id": null,
    "home_page": null,
    "name": "connector-py",
    "maintainer": null,
    "docs_url": null,
    "requires_python": ">=3.10",
    "maintainer_email": null,
    "keywords": "integrations",
    "author": null,
    "author_email": "teamlumos <security@lumos.com>",
    "download_url": "https://files.pythonhosted.org/packages/ba/3b/be14ee9884bebefc637660c4f5a01b1a05a2fa64dc1152db867ed668655f/connector_py-3.2.0.tar.gz",
    "platform": null,
    "description": "# Lumos Connectors\n\n[![PyPI - Version](https://img.shields.io/pypi/v/connector-py.svg)](https://pypi.org/project/connector-py)\n[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/connector-py.svg)](https://pypi.org/project/connector-py)\n\n-----\n\n## Table of Contents\n\n- [Installation](#installation)\n- [Usage](#usage)\n- [Error Handling](#error-handling)\n- [Scaffold](#scaffold)\n- [Unasync](#unasync)\n- [FastAPI](#fastapi)\n- [Tips](#tips)\n- [License](#license)\n\n## Installation\n\n```console\npip install connector-py\n```\n\n## Usage\n\nThe package can be used in three ways:\n1. A CLI to scaffold a custom connector with its own CLI to call commands\n2. A library to create a custom connector\n3. A library to convert your custom connector code to a FastAPI HTTP server\n\nTo get started, run `connector --help`\n\nAn example of running a command that accepts arguments\nin an integration connector called `mock-connector`:\n\n```shell\nmock-connector info --json '{\"a\": 1}'\n```\n\n### Connector implementation\nAll new connectors should be based on the `connector.integration.Integration` class. The new approach doesn't define capabilities by inheriting from connector interface (called\u00a0`LumosCommandMixin`) but injects capability implementations into an instance of `Integration`\u00a0class. This allows us to:\n- typecheck the implementations\n- partially implemented connectors\n- check that implementation accept expected arguments and return expected response\n- have connector specific arguments\n\n```python\nimport httpx\nfrom connector.capability import CapabilityName\nfrom connector.errors import HTTPHandler\nfrom connector.integration import Integration\nfrom connector.serializers.request import (\n    BasicCredentials,\n    ListAccountsRequest,\n    Request,\n)\nfrom connector.serializers.response import (\n    ListAccountsResponse,\n    Response,\n)\n\nintegration = Integration(\n    app_id=\"app_id\",\n    auth=BasicCredentials,\n    exception_handlers=[\n        (httpx.HTTPStatusError, HTTPHandler, None),\n    ],\n    handle_errors=True,\n)\n\n\n@integration.register_capability(CapabilityName.LIST_ACCOUNTS)\nasync def list_accounts(request: Request[ListAccountsRequest, None]) -> Response[ListAccountsResponse]:\n    # do whatever is needed to get accounts\n    return Response[ListAccountsResponse](\n        response=ListAccountsResponse(\n            accounts=accounts,\n        ),\n        raw_data=raw_data if request.include_raw_data else None,\n        ...\n    )\n```\n\n#### Converting LumosCommandMixin-based integrations\n- if you don't need to sync, drop `sync_/` folder; otherwise drop `async_/`\n- in your connector implementation, create instance of `Integration` class, fill-in `app_id`, `exception_handlers` and `auth`\n- all methods that implement capabilities have to be decorated with `integration.register_capability(name=CapabilityName.<pick-correct-name>)`\n- if you don't need any extra arguments for capability parameters (besides auth and pagination, which are now part of request), remove them and use the standard way provided with `connector.serializers.request.Request` class\n- make all tests sync as the `dispatch` method is synchronous and it start the event loop itself\n- you're done\n\n### Error Handling\n\nError handling is facilitated through an exception handler decorator.\nSee `connector/async_/exception_handler.py` and `connector/errors.py`.\n\nAn exception handler can be attached to the connector library as follows:\n\n```python\nfrom httpx import HTTPStatusError\nfrom connector.errors import HTTPHandler\nfrom connector.async_exception_handler import connector_handler\n\nintegration = Integration(\n    ...,\n    exception_handlers=[\n        (HTTPStatusError, HTTPHandler, None),\n    ],\n    handle_errors=True,\n)\n```\n\nThe decorator accepts a list of tuples of three. First tuple argument is the exception you would like to be catching, second is the handler (default or implemented on your own) and third is a specific error code that you would like to associate with this handler.\n\nBy default it is recommended to make use of the default HTTPHandler which will handle `raise_for_status()` for you and properly error code it. For more complex errors it is recommended to subclass the ExceptionHandler (in `connector/errors.py`) and craft your own handler.\n\n#### Making your own handler\n\nTo setup your own handler, you can extend the abstract ExceptionHandler class:\n\n```python\nfrom connector.errors import ExceptionHandler, ErrorCodes\nfrom connector.serializers.lumos import EncounteredErrorResponse\nfrom connector.serializers.response import Response\n\nclass CustomHandler(ExceptionHandler):\n    @staticmethod\n    def handle(\n        e: Exception,\n        original_func: t.Any,\n        response: Response[EncounteredErrorResponse],\n        error_code: str | ErrorCodes | None = None,\n    ) -> Response[EncounteredErrorResponse]:\n        # Perform any custom logic, another call, modify the response, etc.\n        response.error.error_code = \"custom_error_code\"\n        return response\n```\n\n#### Raising an exception\n\nAmong this, there is a custom exception class available as well as a default list of error codes:\n\n```python\nfrom connector.errors import ConnectorError, ErrorCodes\n\ndef some_method(self, args):\n    raise ConnectorError(\"Received wrong data, x: y\", ErrorCodes.BAD_REQUEST)\n```\n\nIt is preferred to raise any manually raisable exception with this class. A connector can implement its own error codes list, which should be properly documented.\n\n### Response\n\nError codes are by default prefixed with the app_id of the connector that has raised the exception. In your implementation you don't need to worry about this and can only focus on the second and optionally third level of the error code.\n\nAn example response when handled this way:\n\n```json\n// BAD_REQUEST error from github connector\n{\"error\":{\"message\":\"Some message\",\"status_code\":400,\"error_code\":\"github.bad_request\",\"raised_by\":\"HTTPStatusError\",\"raised_in\":\"github.sync_.lumos:validate_credentials\"}, \"response\": null, \"raw_data\": null}\n```\n\n### Scaffold\n\nTo scaffold a custom connector, run `connector scaffold --help`\n\nTo scaffold the mock-connector, run\n`connector scaffold mock-connector \"projects/connectors/python/mock-connector\"`\n\n### Unasync\n\n*Unasync will be removed when all connectors are migrated to `Integration` class approach.*\n\nWhen developing this package, start off creating async functions and then\nconvert them to sync functions using `unasync`.\n\n```console\nconnector hacking unasync\n```\n\n### FastAPI\n\nTo convert your custom connector to a FastAPI HTTP server, run `connector hacking http-server`\n\n## Tips\n\n#### The library I want to use is synchronous only\n\nYou can use a package called `asgiref`. This package converts I/O bound synchronous\ncalls into asyncio non-blocking calls. First, add asgiref to your dependencies list\nin `pyproject.toml`. Then, in your async code, use `asgiref.sync_to_async` to convert\nsynchronous calls to asynchronous calls.\n\n```python\nfrom asgiref.sync import sync_to_async\nimport requests\n\nasync def async_get_data():\n    response = await sync_to_async(requests.get)(\"url\")\n```\n\n## License\n\n`connector` is distributed under the terms of the [Apache 2.0](./LICENSE.txt) license.\n",
    "bugtrack_url": null,
    "license": " Apache License Version 2.0, January 2004 http://www.apache.org/licenses/  TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION  1. Definitions.  \"License\" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.  \"Licensor\" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.  \"Legal Entity\" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, \"control\" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.  \"You\" (or \"Your\") shall mean an individual or Legal Entity exercising permissions granted by this License.  \"Source\" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.  \"Object\" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.  \"Work\" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).  \"Derivative Works\" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.  \"Contribution\" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, \"submitted\" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as \"Not a Contribution.\"  \"Contributor\" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.  2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.  3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.  4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:  (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and  (b) You must cause any modified files to carry prominent notices stating that You changed the files; and  (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and  (d) If the Work includes a \"NOTICE\" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.  You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.  5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.  6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.  7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.  8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.  9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.  END OF TERMS AND CONDITIONS  APPENDIX: How to apply the Apache License to your work.  To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets \"[]\" replaced with your own identifying information. (Don't include the brackets!)  The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same \"printed page\" as the copyright notice for easier identification within third-party archives.  Copyright 2024 Lumos App, Inc.  Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at  http://www.apache.org/licenses/LICENSE-2.0  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ",
    "summary": "An Abstract Tool to Perform Actions on Integrations",
    "version": "3.2.0",
    "project_urls": {
        "Documentation": "https://github.com/teamlumos/integration-connectors/#readme",
        "Issues": "https://github.com/teamlumos/integration-connectors/issues",
        "Source": "https://github.com/teamlumos/integration-connectors"
    },
    "split_keywords": [
        "integrations"
    ],
    "urls": [
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "76b834a33be9608f3a0c3e217cfd3c128b765ff1c7e3df551baaaf580e6c8af3",
                "md5": "de7f72e34ede7e58b98c64a9b0cf7cf0",
                "sha256": "2e865ba2d48beca91b9e768f46f1776b6d93b36b6c7f5de1003a9f29c4d060c6"
            },
            "downloads": -1,
            "filename": "connector_py-3.2.0-py3-none-any.whl",
            "has_sig": false,
            "md5_digest": "de7f72e34ede7e58b98c64a9b0cf7cf0",
            "packagetype": "bdist_wheel",
            "python_version": "py3",
            "requires_python": ">=3.10",
            "size": 293056,
            "upload_time": "2024-10-03T20:23:21",
            "upload_time_iso_8601": "2024-10-03T20:23:21.035401Z",
            "url": "https://files.pythonhosted.org/packages/76/b8/34a33be9608f3a0c3e217cfd3c128b765ff1c7e3df551baaaf580e6c8af3/connector_py-3.2.0-py3-none-any.whl",
            "yanked": false,
            "yanked_reason": null
        },
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "ba3bbe14ee9884bebefc637660c4f5a01b1a05a2fa64dc1152db867ed668655f",
                "md5": "6f38f436707f8825bc6e90acf23ba6ad",
                "sha256": "eb38acdd997dd890d8d5feb29bd6cbe84e895571995bdc9d73e98943168a9e81"
            },
            "downloads": -1,
            "filename": "connector_py-3.2.0.tar.gz",
            "has_sig": false,
            "md5_digest": "6f38f436707f8825bc6e90acf23ba6ad",
            "packagetype": "sdist",
            "python_version": "source",
            "requires_python": ">=3.10",
            "size": 93970,
            "upload_time": "2024-10-03T20:23:23",
            "upload_time_iso_8601": "2024-10-03T20:23:23.216451Z",
            "url": "https://files.pythonhosted.org/packages/ba/3b/be14ee9884bebefc637660c4f5a01b1a05a2fa64dc1152db867ed668655f/connector_py-3.2.0.tar.gz",
            "yanked": false,
            "yanked_reason": null
        }
    ],
    "upload_time": "2024-10-03 20:23:23",
    "github": true,
    "gitlab": false,
    "bitbucket": false,
    "codeberg": false,
    "github_user": "teamlumos",
    "github_project": "integration-connectors",
    "github_not_found": true,
    "lcname": "connector-py"
}
        
Elapsed time: 0.36679s