flyteplugins-linear
Receive Linear webhooks in Flyte.
pip install "flyteplugins-linear[app]"
Using it
Hand a LinearProvider() to a WebhookAppEnvironment and register handlers with the
typed constants in events:
import flyte
from flyte.extras.webhooks import WebhookAppEnvironment, run_once
from flyteplugins.linear import LinearProvider, events
# LinearProvider.default_secret_env is mounted for you.
app_env = WebhookAppEnvironment(name="linear-webhooks", providers=[LinearProvider()])
@app_env.on_event(events.Issue.CREATE)
async def handle(event):
import flyte.remote as remote
task = remote.Task.get(name="my-env.my_task", auto_version="latest")
result = await run_once.aio(task, key=event.dedupe_key(), resource=event.resource_id)
if not result.created:
return {"skipped": result.run.name, "url": result.run.url}
return {"run": result.run.name}
flyte.serve(app_env)
Handlers must await run_once.aio(...). The blocking form stalls the
app's event loop, and Linear times deliveries out in seconds.
One app can serve several products at once — hand it one provider per product.
Try it
examples/linear_webhooks.py runs two ways. The first needs no Linear account:
python examples/linear_webhooks.py --local # replay a real sample delivery in-process
python examples/linear_webhooks.py # deploy the receiver to Flyte
--local posts this plugin's SAMPLE_DELIVERY through the app with FastAPI's
test client, so you see a delivery verified, normalized, and dispatched — plus
an unsigned one refused with a 401, and the same delivery replayed to show the
dedupe key is stable.
Setup
- Store the secret and mount it on the app:
flyte create secret LINEAR_WEBHOOK_SECRET --value <secret>
- Point Linear at
<app-url>/webhook/linear, from Linear Settings → API → Webhooks (it shows the signing secret on creation).
Verification: HMAC-SHA256 over the raw body (Linear-Signature).
Comment and reaction payloads carry the team id only on the nested issue; the parser follows it, so a scopes allowlist can still attribute them.
Event constants
events spells every event this plugin can dispatch, as str enums grouped by
event type, so a typo fails at import rather than by silently never matching.
Raw strings still work, for events the constants do not cover yet.
What this plugin does not do
Call the Linear API. Use gql — Linear ships no Python SDK, and its API is a single GraphQL endpoint directly from your tasks — see
examples/external_saas_integrations. This plugin owns only the part that is
Flyte's: authenticating an inbound delivery and turning it into a run.
1 maintainer
Metadata
1 maintainer
Release files for flyteplugins-linear 2.11.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flyteplugins_linear-2.11.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / flyteplugins_linear-2.11.3-py3-none-any.whl
| Download URL | flyteplugins_linear-2.11.3-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1ce753b0e3ef340f5a1a8e720b73e0653eeafe25ddd452caf6e464f785d2cbd
|
|
BLAKE2b-256 checksum How to use checksums |
948a46542fdf1bd8d33706d2f753c49083342bfc2050846537ce7b88cfba9ab7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for flyteplugins-linear 2.11.3
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.
