Automatic Logging for Faster, Secure Debugging
Blog post from Pulumi
Pulumi v3.254.0 adds automatic encrypted logging for every operation, reducing the need to reproduce failures solely to collect diagnostic information for support. Logs are stored in `$PULUMI_HOME/logs`, encrypted with the relevant stack’s secrets manager when available, and use gzip compression with AES-256-GCM encryption; logs without a secrets manager are compressed without including property-value secrets. To limit disk use, logs are removed after seven days or once the directory exceeds 500 MB, with configurable retention settings, and users can decrypt local logs through `pulumi logs decrypt` when the appropriate stack secrets manager is available. The new `pulumi logs share` command re-encrypts logs with a server-managed key and redacts secrets by default, enabling users to securely share diagnostic files with Pulumi employees through even potentially unsafe channels such as GitHub issues.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Secrets Management | 4 | 2,244 | 480 | 132 | -13% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.