Skip to main content

Hotglue SDK for Taps

This is a fork of Melanto's SingerSDK for special use in hotglue, an embedded integration platform for running Singer Taps and Targets.

Taps and targets built on the SDK are automatically compliant with the Singer Spec, the de-facto open source standard for extract and load pipelines.

OAuth Access Token Support

Taps can implement the --access-token CLI flag to refresh OAuth access tokens without running the tap directly.

Implementing Access Token Support

To enable this feature in your tap, override the access_token_support class method to return a tuple of (authenticator_class, auth_endpoint):

from hotglue_singer_sdk import Tap
from my_tap.auth import MyOAuthAuthenticator

class MyTap(Tap):
    name = "tap-myservice"

    @classmethod
    def access_token_support(cls, connector=None):
        """Return the authenticator class and auth endpoint for token refresh.

        Returns:
            A tuple of (authenticator_class, auth_endpoint).
        """
        default_url = "https://api.myservice.com/oauth/token"
        # ommit if token url is not dynamic
        dynamic_url = connector.config.get("auth_url")
        url = dynamic_url or default_url
        return (MyOAuthAuthenticator, url)

Authenticator Requirements

The authenticator class must implement the following methods:

  • is_token_valid() - Returns True if the current access token is still valid
  • update_access_token() - Refreshes the access token and updates the config file

The authenticator will be instantiated with these parameters:

  • stream - A dummy stream object with logger, tap_name, and config attributes
  • config_file - Path to the config file for writing updated tokens
  • auth_endpoint - The OAuth token endpoint URL

Usage

Once implemented, users can refresh the access token using:

tap-myservice --config config.json --access-token

This will output the new access token as JSON:

{
  "access_token": "new_token_value"
}

Note: The --access-token flag requires a config file path. It will not work with --config ENV or when omitting the config.

Metadata

Release files for hotglue-singer-sdk 1.0.53

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hotglue-singer-sdk 1.0.53
File Size Uploaded Provenance Actions
hotglue_singer_sdk-1.0.53.tar.gz 116.4 kB Without provenance Details for hotglue_singer_sdk-1.0.53.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for hotglue-singer-sdk 1.0.53
File Interpreter ABI Platform Actions
hotglue_singer_sdk-1.0.53-py3-none-any.whl Python 3 none any Details for hotglue_singer_sdk-1.0.53-py3-none-any.whl

Total release size: 259.4 kB

Release files / hotglue_singer_sdk-1.0.53.tar.gz

Download URL hotglue_singer_sdk-1.0.53.tar.gz
Size 116.4 kB
Tags Source
SHA-256 checksum
How to use checksums
1b13d902eb429122eaadd0622b1134e501b136794a2313f36b4354c707d96dbc
BLAKE2b-256 checksum
How to use checksums
7a7b1df9ac6e2298b8555caa984acb53f619dfb87f0e1bedb0c35c15b53469fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.10.22

Release files / hotglue_singer_sdk-1.0.53-py3-none-any.whl

Download URL hotglue_singer_sdk-1.0.53-py3-none-any.whl
Size 143.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
613bbe12d91dcbc94f05e7a2ee427aba890ff1c7ca9388bbab50d1b1ff9be6ea
BLAKE2b-256 checksum
How to use checksums
e7528f4920cfc2ff8fa41cc4ae0236554951982d7d93f1db35fc95ec791b65e3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.10.22

Security for hotglue-singer-sdk 1.0.53

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.

Release history Release notifications | RSS feed

This release

1.0.53 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page