render-lab-tasks-render
Fifteen Render control-plane tasks for services, deploys, Postgres, Key Value,
projects, and diagnostics. Import render_lab_tasks_render.tasks to register;
every operation also exports injectable async *_impl(ctx, input, *, deps=...).
RENDER_API_KEY is read lazily. Provision/create operations accept ownerId or
use RENDER_OWNER_ID. Pass explicit ownerId for name-based lookup scoping and
environmentId for project placement. Names are not a concurrency-safe unique
key: simultaneous creators or matches beyond the first 20 results need care.
render.provisionService uses ctx.run on the wrapped render.ensureService
child. The checkpointed ensure phase does not repeat on every deploy poll.
Terminal deploy failure returns live=false; pending states throw to drive the
durable retry. Inject a context runner plus the read port for composition tests.
Other awaiters retain source error-message/retry behavior, including source
messages built before status reads (created/undefined in progress messages).
Service reconciliation checks managed serviceDetails fields. Environment-only, repository, or branch drift does not trigger reconciliation, matching TS. Docker commands use envSpecificDetails; image sources are top-level and exclude repo.
Python uses durable retries only; the source's in-process 429/5xx exception is not reproduced. This matches the Python repository's single retry owner rule. Diagnostics actually clips UTF-8 log message bytes to maxBytes rather than the source's ineffective drop-one-line heuristic. These deviations and required live checks are recorded in ADR-0013 and the shared testing backlog.
No resources are created by importing the package. Live control-plane writes, project placement, quota handling, and durable checkpoint replay remain unverified. Any new Render-DX test services must belong to taskpack-test/testing.
Deps.ensure_service can inject the provisioning creation collaborator. If omitted
on custom dependencies, the injected port handles creation. Default wrapped calls
continue to checkpoint render.ensureService through ctx.run.
Installation
pip install render-lab-tasks-render==0.1.0
1 maintainer
Metadata
1 maintainer
Release files for render-lab-tasks-render 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| render_lab_tasks_render-0.1.0.tar.gz | 11.0 kB | With provenance | Details for render_lab_tasks_render-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| render_lab_tasks_render-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for render_lab_tasks_render-0.1.0-py3-none-any.whl |
Total release size: 30.1 kB
Release files / render_lab_tasks_render-0.1.0.tar.gz
| Download URL | render_lab_tasks_render-0.1.0.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c126255bd22e64a77c66a31f94dd5001cdb4bf4adb43c2f6d2b7a8a2decd5b00
|
|
BLAKE2b-256 checksum How to use checksums |
394c38874b030b09fa4b8b5ab4924b3772782bf9d6c272e15e8d785396c5ab27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / render_lab_tasks_render-0.1.0-py3-none-any.whl
| Download URL | render_lab_tasks_render-0.1.0-py3-none-any.whl |
|---|---|
| Size | 19.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaffe8f32f1c019a87f8850ad563b93a5049025e9e112d8d8e5f71a1910f8bfc
|
|
BLAKE2b-256 checksum How to use checksums |
fedc765109b07cad7bb8a1b896eb73639fc230bc54139e3d015a143d77ab9267
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logSecurity for render-lab-tasks-render 0.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for render_lab_tasks_render-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logA 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.
