Logfire Resource Provider
Manage Pydantic Logfire projects, alerts, dashboards, channels, and API tokens with Pulumi.
Installing
This package is available for several languages/platforms:
Node.js (JavaScript/TypeScript)
To use from JavaScript or TypeScript in Node.js, install using either npm:
npm install @pydantic/pulumi-logfire
or yarn:
yarn add @pydantic/pulumi-logfire
Python
To use from Python, install using pip:
pip install pydantic-pulumi-logfire
Import it in code as pulumi_logfire.
Go
To use from Go, use go get to grab the latest version of the library:
go get github.com/pydantic/pulumi-logfire/sdk/go/logfire
Configuration
The following configuration points are available for the logfire provider:
logfire:baseUrl(environment:LOGFIRE_BASE_URL) – Optional override for the Logfire API base URL. If omitted, the provider usesLOGFIRE_BASE_URLor infers the SaaS endpoint from the API key region. Self-hosted customers should set this explicitly.logfire:apiKey(environment:LOGFIRE_API_KEY) – Bearer token for the Logfire API.
Example stack config:
pulumi config set --secret logfire:apiKey pylf_v2_us_...
# Self-hosted only:
# pulumi config set logfire:baseUrl https://<self-hosted-logfire>
For Logfire SaaS, the provider infers https://logfire-us.pydantic.dev or https://logfire-eu.pydantic.dev from the API key region. If you set logfire:baseUrl or LOGFIRE_BASE_URL, that value is used instead.
Importing existing resources
Existing Logfire resources can be imported into Pulumi state with pulumi import. For resources that are easy to look up by name or slug, prefer the name-based import IDs:
| Resource | Recommended import ID | Example |
|---|---|---|
logfire:Project |
organization/project-name |
pulumi import logfire:index/project:Project prod "acme/prod-logs" |
logfire:Alert |
project-name/alert-name |
pulumi import logfire:index/alert:Alert errors "prod-logs/error-alert" |
logfire:Dashboard |
project-name/dashboard-slug |
pulumi import logfire:index/dashboard:Dashboard overview "prod-logs/prod-overview" |
UUID-based import IDs are also supported if you already have the backend IDs. The separators /, ,, and | are accepted for multi-part import IDs.
Reference
For detailed reference documentation, please visit the Pulumi registry.
Resources
- Projects (
logfire:Project) - Channels (
logfire:Channel) - Alerts (
logfire:Alert) - Dashboards (
logfire:Dashboard) - Write tokens (
logfire:WriteToken) - Read tokens (
logfire:ReadToken) - Organizations (
logfire:Organization)
Metadata
Release files for pydantic-pulumi-logfire 0.2.2
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 |
|---|---|---|---|---|
| pydantic_pulumi_logfire-0.2.2.tar.gz | 48.8 kB | Without provenance | Details for pydantic_pulumi_logfire-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pydantic_pulumi_logfire-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for pydantic_pulumi_logfire-0.2.2-py3-none-any.whl |
Total release size: 115.6 kB
Release files / pydantic_pulumi_logfire-0.2.2.tar.gz
| Download URL | pydantic_pulumi_logfire-0.2.2.tar.gz |
|---|---|
| Size | 48.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14951838ffd035057d7618796eb24c1b802d0b7d51b52efedfa711de18ed8647
|
|
BLAKE2b-256 checksum How to use checksums |
8b0c848cf5ab16fe58038fc82e919d52ffdbcc287f9cd60a8e0fccf621b23a70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.8
|
Release files / pydantic_pulumi_logfire-0.2.2-py3-none-any.whl
| Download URL | pydantic_pulumi_logfire-0.2.2-py3-none-any.whl |
|---|---|
| Size | 66.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d21a6ee80547e768ed6a705609e9f9afbcd475c315564d2c4ba8bc4eb3b8085d
|
|
BLAKE2b-256 checksum How to use checksums |
75681e4329d4fec77d46fc6d6d0a2bde41a418eb858acf3076508e6e7bf148be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.8
|
Security for pydantic-pulumi-logfire 0.2.2
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.