Saravanan666/pypi-org huggingface dataset:
Package: airbugmaker
一、安装（python版本建议3.7以上）pipinstalldubborequests二、升级包pipinstall--upgradedubborequests三、示例获取dubbo服务详情# 导入importdubborequests# 获取dubbo服务详情data=dubborequests.search('cn.com.xxx.sso.ehr.api.dubbo.SsoEmpInfoService')获取服务下的所有方法# 导入importdubborequests# 获取dubbo服务下的所有方法data=dubborequests.list('cn.com.xxx.sso.ehr.api.dubbo.SsoEmpInfoService')# 获取dubbo服务指定的方法data=dubborequests.list('cn.com.xxx.sso.ehr.api.dubbo.SsoEmpInfoService','login')通过zookeeper获取服务的ip和端口, Telnet命令测试dubbo接口importdubborequestsfromdubborequestsimportConfig# 先配置zookeeper中心地址Config.zookeeper_url_list=['192.168.240.15:2181','192.168.240.15:2182','192.168.240.15:2183']invoke_data={"service_name":"cn.com.xxxxx.sso.ehr.api.dubbo.SsoEmpInfoService","method_name":"login","data":{"account":"xxxx","password":"xxxx"}}# 通过zookeeper获取服务的ip和端口, Telnet命令测试dubbo接口data=dubborequests.zk_invoke(*invoke_data)Telnet命令测试dubbo接口importdubborequestsinvoke_data={"ip":'xxxx',"port":7777,"service_name":"cn.com.xxxxx.sso.ehr.api.dubbo.SsoEmpInfoService","method_name":"login","data":{"account":"xxxx","password":"xxxx"}}# Telnet命令测试dubbo接口data=dubborequests.telnet_invoke(*invoke_data)
Package: airbyte
PyAirbytePyAirbyte brings the power of Airbyte to every Python developer.Secrets ManagementPyAirbyte can auto-import secrets from the following sources:Environment variables.Variables defined in a local.env("Dotenv") file.Google Colab secrets.Manual entry viagetpass.Note: Additional secret store options may be supported in the future.More info here.Retrieving Secretsfromairbyteimportget_secret,SecretSourcesource=get_connection("source-github")source.set_config("credentials":{"personal_access_token":get_secret("GITHUB_PERSONAL_ACCESS_TOKEN"),})Theget_secret()function accepts an optionalsourceargument of enum typeSecretSource. If omitted or set toSecretSource.ANY, PyAirbyte will search all available secrets sources. Ifsourceis set to a specific source, then only that source will be checked. If a list ofSecretSourceentries is passed, then the sources will be checked using the provided ordering.By default, PyAirbyte will prompt the user for any requested secrets that are not provided via other secret managers. You can disable this prompt by passingprompt=Falsetoget_secret().Connector compatibilityTo make a connector compatible with PyAirbyte, the following requirements must be met:The connector must be a Python package, with apyproject.tomlor asetup.pyfile.In the package, there must be arun.pyfile that contains arunmethod. This method should read arguments from the command line, and run the connector with them, outputting messages to stdout.Thepyproject.tomlorsetup.pyfile must specify a command line entry point for therunmethod calledsource-<connector name>. This is usually done by adding aconsole_scriptssection to thepyproject.tomlfile, or aentry_pointssection to thesetup.pyfile. For example:[tool.poetry.scripts]source-my-connector="my_connector.run:run"setup(...entry_points={'console_scripts':['source-my-connector = my_connector.run:run',],},...)To publish a connector to PyPI, specify thepypisection in themetadata.yamlfile. For example:data:# ...remoteRegistries:pypi:enabled:truepackageName:"airbyte-source-my-connector"Validating source connectorsTo validate a source connector for compliance, theairbyte-lib-validate-sourcescript can be used. It can be used like this:airbyte-lib-validate-source—connector-dir.-—sample-configsecrets/config.jsonThe script will install the python package in the provided directory, and run the connector against the provided config. The config should be a valid JSON file, with the same structure as the one that would be provided to the connector in Airbyte. The script will exit with a non-zero exit code if the connector fails to run.For a more lightweight check, the--validate-install-onlyflag can be used. This will only check that the connector can be installed and returns a spec, no sample config required.ContributingTo learn how you can contribute to PyAirbyte, please see ourPyAirbyte Contributors Guide.Changelog and Release NotesFor a version history and list of all changes, please see ourGitHub Releasespage.
Package: airbyte-api-wrapper
Python wrapper for APIFull API spec of the API can be found here:https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.htmlHow to useCreate clientfrom airbyte_python_helper import AirbyteHelper
import os

airbyte_url = os.environ["AIRBYTE_URL"]
airbyte_client_id = os.environ["CLIENT_ID"]
airbyte_client_secret = os.environ["CLIENT_SECRET"]

airbyte_client = AirbyteHelper(
airbyte_url, airbyte_client_id, airbyte_client_secret
)Destinationswid = airbyte_client.get_first_workspace_id()
print("workspaceId", wid)
print(airbyte_client.list_destinations(wid))

for destination in airbyte_client.list_destinations(wid):
    airbyte_client.delete_destination(destination["destinationId"])

sources = airbyte_client.list_sources(wid)Sourceswid = airbyte_client.get_first_workspace_id()
print("workspaceId", wid)
sources = airbyte_client.list_sources(wid)
print(sources)
for source in sources:
    print(source["sourceId"])Workspacesworkspaces = airbyte_client.list_workspaces()
print(workspaces)
Package: airbyte-cdk-PHLAIR
Connector Development Kit (Python)The Airbyte Python CDK is a framework for rapidly developing production-grade Airbyte connectors. The CDK currently offers helpers specific for creating Airbyte source connectors for:HTTP APIs (REST APIs, GraphQL, etc..)Singer TapsGeneric Python sources (anything not covered by the above)The CDK provides an improved developer experience by providing basic implementation structure and abstracting away low-level glue boilerplate.This document is a general introduction to the CDK. Readers should have basic familiarity with theAirbyte Specificationbefore proceeding.Getting StartedGenerate an empty connector using the code generator. First clone the Airbyte repository then from the repository root runcd airbyte-integrations/connector-templates/generator
./generate.shthen follow the interactive prompt. Next, find allTODOs in the generated project directory -- they're accompanied by lots of comments explaining what you'll need to do in order to implement your connector. Upon completing all TODOs properly, you should have a functioning connector.Additionally, you can followthis tutorialfor a complete walkthrough of creating an HTTP connector using the Airbyte CDK.Concepts & DocumentationSee theconcepts docsfor a tour through what the API offers.Example ConnectorsHTTP Connectors:Exchangerates APIStripeSlackSinger connectors:SalesforceGithubSimple Python connectors using the barebonesSourceabstraction:Google SheetsMailchimpContributingFirst time setupWe assumepythonpoints to python >=3.9.Setup a virtual env:python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]" # [dev] installs development-only dependenciesIterationIterate on the code locallyRun tests viapytest -s unit_testsPerform static type checks usingmypy airbyte_cdk.MyPyconfiguration is in.mypy.ini.Thetype_check_and_test.shscript bundles both type checking and testing in one convenient command. Feel free to use it!TestingAll tests are located in theunit_testsdirectory. Runpytest --cov=airbyte_cdk unit_tests/to run them. This also presents a test coverage report.Publishing a new version to PyPiBump the package version insetup.pyOpen a PRAn Airbyte member must comment/publish-cdk dry-run=trueto publish the package to test.pypi.org or/publish-cdk dry-run=falseto publish it to the real index of pypi.org.Coming SoonFull OAuth 2.0 support (including refresh token issuing flow via UI or CLI)Airbyte Java HTTP CDKCDK for Async HTTP endpoints (request-poll-wait style endpoints)CDK for other protocolsDon't see a feature you need?Create an issue and let us know how we can help!
Package: airbyte-cdk-test
Connector Development Kit (Python CDK)The Airbyte Python CDK is a framework for rapidly developing production-grade Airbyte connectors.
The CDK currently offers helpers specific for creating Airbyte source connectors for:HTTP APIs (REST APIs, GraphQL, etc..)Singer TapsGeneric Python sources (anything not covered by the above)The CDK provides an improved developer experience by providing basic implementation structure and abstracting away low-level glue boilerplate.This document is a general introduction to the CDK. Readers should have basic familiarity with theAirbyte Specificationbefore proceeding.Getting StartedGenerate an empty connector using the code generator. First clone the Airbyte repository then from the repository root runcd airbyte-integrations/connector-templates/generator
npm run generatethen follow the interactive prompt. Next, find allTODOs in the generated project directory -- they're accompanied by lots of comments explaining what you'll need to do in order to implement your connector. Upon completing all TODOs properly, you should have a functioning connector.Additionally, you can followthis tutorialfor a complete walkthrough of creating an HTTP connector using the Airbyte CDK.Concepts & DocumentationSee theconcepts docsfor a tour through what the API offers.Example ConnectorsHTTP Connectors:Exchangerates APIStripeSlackSinger connectors:SalesforceGithubSimple Python connectors using the barebonesSourceabstraction:Google SheetsMailchimpContributingFirst time setupWe assumepythonpoints to python >=3.7.Setup a virtual env:python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]" # [dev] installs development-only dependenciesIterationIterate on the code locallyRun tests viapytest -s unit_testsPerform static type checks usingmypy airbyte_cdk.MyPyconfiguration is in.mypy.ini.Thetype_check_and_test.shscript bundles both type checking and testing in one convenient command. Feel free to use it!TestingAll tests are located in theunit_testsdirectory. Runpytest --cov=airbyte_cdk unit_tests/to run them.
This also presents a test coverage report.Publishing a new version to PyPiBump the package version insetup.pyOpen a PRAn Airbyte member must comment/publish-cdk --dry-run=<true or false>. Dry runs publish to test.pypi.org.Coming SoonFull OAuth 2.0 support (including refresh token issuing flow via UI or CLI)Airbyte Java HTTP CDKCDK for Async HTTP endpoints (request-poll-wait style endpoints)CDK for other protocolsGeneral CDK for DestinationsDon't see a feature you need?Create an issue and let us know how we can help!
Package: airbyte-cdk-velocity
Connector Development Kit (Python)The Airbyte Python CDK is a framework for rapidly developing production-grade Airbyte connectors. The CDK currently offers helpers specific for creating Airbyte source connectors for:HTTP APIs (REST APIs, GraphQL, etc..)Singer TapsGeneric Python sources (anything not covered by the above)The CDK provides an improved developer experience by providing basic implementation structure and abstracting away low-level glue boilerplate.This document is a general introduction to the CDK. Readers should have basic familiarity with theAirbyte Specificationbefore proceeding.Getting StartedGenerate an empty connector using the code generator. First clone the Airbyte repository then from the repository root runcd airbyte-integrations/connector-templates/generator
./generate.shthen follow the interactive prompt. Next, find allTODOs in the generated project directory -- they're accompanied by lots of comments explaining what you'll need to do in order to implement your connector. Upon completing all TODOs properly, you should have a functioning connector.Additionally, you can followthis tutorialfor a complete walkthrough of creating an HTTP connector using the Airbyte CDK.Concepts & DocumentationSee theconcepts docsfor a tour through what the API offers.Example ConnectorsHTTP Connectors:Exchangerates APIStripeSlackSinger connectors:SalesforceGithubSimple Python connectors using the barebonesSourceabstraction:Google SheetsMailchimpContributingFirst time setupWe assumepythonpoints to python >=3.7.Setup a virtual env:python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]" # [dev] installs development-only dependenciesIterationIterate on the code locallyRun tests viapytest -s unit_testsPerform static type checks usingmypy airbyte_cdk.MyPyconfiguration is in.mypy.ini.Thetype_check_and_test.shscript bundles both type checking and testing in one convenient command. Feel free to use it!TestingAll tests are located in theunit_testsdirectory. Runpytest --cov=airbyte_cdk unit_tests/to run them. This also presents a test coverage report.Publishing a new version to PyPiBump the package version insetup.pyOpen a PRAn Airbyte member must comment/publish-cdk dry-run=trueto publish the package to test.pypi.org or/publish-cdk dry-run=falseto publish it to the real index of pypi.org.Coming SoonFull OAuth 2.0 support (including refresh token issuing flow via UI or CLI)Airbyte Java HTTP CDKCDK for Async HTTP endpoints (request-poll-wait style endpoints)CDK for other protocolsDon't see a feature you need?Create an issue and let us know how we can help!
Package: airbyte-cdk-velocity-amazon
Connector Development Kit (Python)The Airbyte Python CDK is a framework for rapidly developing production-grade Airbyte connectors. The CDK currently offers helpers specific for creating Airbyte source connectors for:HTTP APIs (REST APIs, GraphQL, etc..)Singer TapsGeneric Python sources (anything not covered by the above)The CDK provides an improved developer experience by providing basic implementation structure and abstracting away low-level glue boilerplate.This document is a general introduction to the CDK. Readers should have basic familiarity with theAirbyte Specificationbefore proceeding.Getting StartedGenerate an empty connector using the code generator. First clone the Airbyte repository then from the repository root runcd airbyte-integrations/connector-templates/generator
./generate.shthen follow the interactive prompt. Next, find allTODOs in the generated project directory -- they're accompanied by lots of comments explaining what you'll need to do in order to implement your connector. Upon completing all TODOs properly, you should have a functioning connector.Additionally, you can followthis tutorialfor a complete walkthrough of creating an HTTP connector using the Airbyte CDK.Concepts & DocumentationSee theconcepts docsfor a tour through what the API offers.Example ConnectorsHTTP Connectors:Exchangerates APIStripeSlackSinger connectors:SalesforceGithubSimple Python connectors using the barebonesSourceabstraction:Google SheetsMailchimpContributingFirst time setupWe assumepythonpoints to python >=3.7.Setup a virtual env:python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]" # [dev] installs development-only dependenciesIterationIterate on the code locallyRun tests viapytest -s unit_testsPerform static type checks usingmypy airbyte_cdk.MyPyconfiguration is in.mypy.ini.Thetype_check_and_test.shscript bundles both type checking and testing in one convenient command. Feel free to use it!TestingAll tests are located in theunit_testsdirectory. Runpytest --cov=airbyte_cdk unit_tests/to run them. This also presents a test coverage report.Publishing a new version to PyPiBump the package version insetup.pyOpen a PRAn Airbyte member must comment/publish-cdk dry-run=trueto publish the package to test.pypi.org or/publish-cdk dry-run=falseto publish it to the real index of pypi.org.Coming SoonFull OAuth 2.0 support (including refresh token issuing flow via UI or CLI)Airbyte Java HTTP CDKCDK for Async HTTP endpoints (request-poll-wait style endpoints)CDK for other protocolsDon't see a feature you need?Create an issue and let us know how we can help!
Package: airbyte-source-activecampaign
Activecampaign SourceThis is the repository for the Activecampaign configuration based source connector.
For information about how to use this connector within Airbyte, seethe documentation.If you are a community contributor, follow the instructions in thedocumentationto generate the necessary credentials. Then create a filesecrets/config.jsonconforming to thesource_activecampaign/spec.yamlfile.
Note that any directory namedsecretsis gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
Seeintegration_tests/sample_config.jsonfor a sample config file.If you are an Airbyte core member, copy the credentials in Lastpass under the secret namesource activecampaign test credsand place them intosecrets/config.json.Viaairbyte-ci(recommended):airbyte-ciconnectors--name=source-activecampaignbuildAn image will be built with the tagairbyte/source-activecampaign:dev.Viadocker build:dockerbuild-tairbyte/source-activecampaign:dev.Then run any of the connector commands as follows:docker run --rm airbyte/source-activecampaign:dev spec
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-activecampaign:dev check --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-activecampaign:dev discover --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-activecampaign:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.jsonYou can run our full test suite locally usingairbyte-ci:airbyte-ciconnectors--name=source-activecampaigntestCustomizeacceptance-test-config.ymlfile to configure tests. SeeConnector Acceptance Testsfor 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 insetup.py, NOTrequirements.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 toMAIN_REQUIREMENTSlist.required for the testing need to go toTEST_REQUIREMENTSlistYou've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?Make sure your changes are passing our test suite:airbyte-ci connectors --name=source-activecampaign testBump the connector version inmetadata.yaml: increment thedockerImageTagvalue. Please followsemantic versioning for connectors.Make sure themetadata.yamlcontent is up to date.Make the connector documentation and its changelog is up to date (docs/integrations/sources/activecampaign.md).Create a Pull Request: useour PR naming conventions.Pat yourself on the back for being an awesome contributor.Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
Package: airbyte-source-aha
Aha SourceThis is the repository for the Aha configuration based source connector.
For information about how to use this connector within Airbyte, seethe documentation.If you are a community contributor, follow the instructions in thedocumentationto generate the necessary credentials. Then create a filesecrets/config.jsonconforming to thesource_aha/spec.yamlfile.
Note that any directory namedsecretsis gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
Seeintegration_tests/sample_config.jsonfor a sample config file.If you are an Airbyte core member, copy the credentials in Lastpass under the secret namesource aha test credsand place them intosecrets/config.json.Viaairbyte-ci(recommended):airbyte-ciconnectors--name=source-ahabuildAn image will be built with the tagairbyte/source-aha:dev.Viadocker build:dockerbuild-tairbyte/source-aha:dev.Then run any of the connector commands as follows:docker run --rm airbyte/source-aha:dev spec
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-aha:dev check --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-aha:dev discover --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-aha:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.jsonYou can run our full test suite locally usingairbyte-ci:airbyte-ciconnectors--name=source-ahatestCustomizeacceptance-test-config.ymlfile to configure tests. SeeConnector Acceptance Testsfor 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 insetup.py, NOTrequirements.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 toMAIN_REQUIREMENTSlist.required for the testing need to go toTEST_REQUIREMENTSlistYou've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?Make sure your changes are passing our test suite:airbyte-ci connectors --name=source-aha testBump the connector version inmetadata.yaml: increment thedockerImageTagvalue. Please followsemantic versioning for connectors.Make sure themetadata.yamlcontent is up to date.Make the connector documentation and its changelog is up to date (docs/integrations/sources/aha.md).Create a Pull Request: useour PR naming conventions.Pat yourself on the back for being an awesome contributor.Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.