Skip to main content

etlantic-rsconnect

Optional Posit Connect deployment, schedule, and HTTPS trigger integration for ETLantic. The generated Quarto content contains a small standard-library runner; it does not install FastAPI, Data Mover, ETL engines, pipeline definitions, or source and sink credentials.

Install the package and optional Posit SDK with:

pip install 'etlantic-rsconnect[connect]'

The deployment host also needs Quarto and rsconnect-python 1.31.1 or newer. Those are external deployment tools, not runtime dependencies of this Python package. RsconnectPythonDeployer targets one explicit HTTPS Connect URL. It resolves separate deployment and trigger credential references only at the authorized boundary, passes values through the child environment, and never puts credentials in command arguments or surfaced CLI output. Supply a durable DeploymentJournal; a timed-out or ambiguous publish is recorded as uncertain and must be reconciled before retrying.

build_trigger_bundle creates a deterministic Quarto project whose pre-render hook runs the standalone delivery script on every render. The archive includes the explicit receiver URL, schedule references, outbound bounds, and a secret reference, but no credential value. The bundle keeps execution caching off and an empty, comment-only requirements.txt, so deployment does not infer the ETLantic development environment as content dependencies. The deployer sets ETLANTIC_TRIGGER_ARMED=false during publish, so build and deployment renders do not submit a trigger.

The receiver client uses public etlantic.control_plane trigger/1 values and etlantic.outbound policy. It pins HTTPS connections to the resolved, policy-checked addresses; rejects redirects; enforces bounded attempts, elapsed time, and response bytes; validates exact receipt schema and correlation; and retries the same occurrence. reconcile() looks up the retained receipt for that same occurrence after an uncertain delivery. A missing receipt returns None; callers may retry with the same envelope, never a newly derived slot. OccurrenceContext must come from a trusted integration and contains canonical scheduled UTC time plus stable delivery-attempt and correlation identifiers. Public limits cap a delivery at 10 attempts, 60 seconds per request, 300 seconds total, 1 MiB of response data, and 60 seconds of Retry-After delay; the defaults are 3 attempts, 10 seconds, 30 seconds, 64 KiB, and 5 seconds.

The elapsed budget includes DNS, credential lookup, and response reads. Secret resolvers run in background threads with the caller's contextvars and must support that calling convention. Timed-out results are discarded. Each process allows at most four outstanding DNS workers and four credential workers; a saturated resolver fails closed rather than creating more workers.

PositSdkGateway wraps the public Posit Python SDK schedule and content environment surfaces. Schedule mutations are experimental, so ConnectScheduleAdapter refuses them unless allow_experimental_schedule_api=True is explicitly set. The adapter requires a durable, full-record compare-and-swap BindingStore, journals pending mutations before Connect writes, disables the generated content before timer changes, and retains pending state after uncertain results. Binding stores must make compare-and-swap atomic across processes. A pending registration is explicitly marked in its operation metadata. A claimed pending operation cannot be taken over while its writer may still be running. Exact Connect readback is only a snapshot and does not establish that the writer has stopped, so retries leave claimed operations pending for operator reconciliation. Resume failure first changes the claim atomically to a pending rollback before it disarms content or pauses the canonical schedule. The SDK gateway owns a client copy pinned to the validated server URL, so mutations to the caller's client configuration do not redirect its requests. It supports the UTC interval subset exactly representable by Connect's minute, hour, and day schedule types. For new content, deploy first, pass the successful deployment result and bundle to register_deployed_content(), then call apply() with the returned pending binding. Registration rejects content that already has a schedule; activation verifies Connect's resulting rule before arming the content. inspect_drift() is read-only and reports when the SDK's decoded recurrence cannot be compared.

The generated bundle cannot currently be activated as an ETL trigger. The documented Connect scheduled-render path does not provide a trusted nominal slot and retry identity, and the package does not invent one from render time or static environment variables. The generated runner therefore refuses delivery when armed because no qualified occurrence-context provider is in the bundle. The experimental schedule API, durable ownership/journal implementations, independent receiver and worker, and live Connect lifecycle also remain unqualified. These are production support qualification items, not prerequisites for distributing the package as a preview. The preview does not claim active scheduled delivery or production support.

See the 0.60 implementation plan and Connect integration plan for the remaining platform decisions and evidence gates.

The preview has its own release notes and tag: etlantic-rsconnect-v0.60.0. It can be published while the core remains at 0.59.0. The preview exit record lists the local checks and publishing procedure. BindingStore, ConnectScheduleGateway, and DeploymentJournal are public root imports for host integrations; storage implementations must provide the documented durable and atomic behavior.

The local simulation design records SDK, scheduling, HTTPS, and crash-recovery simulations that run without a Connect server. The regression suite covers SDK recurrence normalization, resume-anchor preservation, bounded DNS and credential resolution, and actual verified loopback TLS deadlines through closing-response handoff. Live Connect qualification remains relevant to production support claims, not package distribution.

Metadata

Release files for etlantic-rsconnect 0.60.0

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

Source distribution (sdist)

Source distribution for etlantic-rsconnect 0.60.0
File Size Uploaded Provenance Actions
etlantic_rsconnect-0.60.0.tar.gz 34.6 kB Without provenance Details for etlantic_rsconnect-0.60.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for etlantic-rsconnect 0.60.0
File Interpreter ABI Platform Actions
etlantic_rsconnect-0.60.0-py3-none-any.whl Python 3 none any Details for etlantic_rsconnect-0.60.0-py3-none-any.whl

Total release size: 73.3 kB

Release files / etlantic_rsconnect-0.60.0.tar.gz

Download URL etlantic_rsconnect-0.60.0.tar.gz
Size 34.6 kB
Tags Source
SHA-256 checksum
How to use checksums
ecd3733ad85b3c5ed88578294fe8f1831d7b7705877c307e83d0df5afe8d726e
BLAKE2b-256 checksum
How to use checksums
b2a6d82334b571be9902ede8f77b8220076d971d1d7c9a6ab726d7262c92caa3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.0 {"installer":{"name":"uv","version":"0.12.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / etlantic_rsconnect-0.60.0-py3-none-any.whl

Download URL etlantic_rsconnect-0.60.0-py3-none-any.whl
Size 38.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
48e5ca361bb3e7c596fec4c346f6f0f90c3cdf350a95a346a20f5462f466a1b4
BLAKE2b-256 checksum
How to use checksums
2c74cdb38e04161f3fc2662c445a693c71af927839944708bed22eaca6cfe7b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.0 {"installer":{"name":"uv","version":"0.12.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for etlantic-rsconnect 0.60.0

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

0.60.0 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