Pulumi

Public discussion around Pulumi over the four-week window was heavily skewed toward frustration, with bugs and missing features accounting for the majority of mentions. Commenters surfaced issues ranging from provider panics when importing resources with write-only Terraform fields to incorrect behavior around stack finalizers and destroy operations. Several mentions pointed to documentation gaps, such as the absence of a note clarifying that skipAwait defaults to false, suggesting that even when core functionality works, the surrounding guidance was perceived as incomplete or misleading.

The score trajectory tells a story of modest but unsteady recovery. Discussion started at a low point in mid-May, then climbed slightly and held a narrow plateau through late May and into early June. A brief uptick appeared in mid-June before edging back down in the final week, leaving the overall window score essentially flat against the prior period. The movement was small enough that commenters do not appear to have experienced any breakthrough improvement, and the recovery looked tentative rather than sustained.

Feature requests and missing capabilities generated substantial noise alongside the bug reports. Commenters raised gaps around cloud backend support for providers like Alibaba Cloud OSS, geo recovery options for certain service namespaces, and SDK type safety for non-primitive inputs. These threads reflected a sense among some participants that the product's surface area was not keeping pace with where they needed to take their infrastructure.

Opinion was divided on the severity framing. A small number of mentions treated Pulumi in a more neutral or illustrative light, referencing it as one viable framework among several for standard patterns like serverless APIs. That contrast with the bug-heavy majority of discussion suggested the community contained both active troubleshooters and observers using the product as a reference point, producing a split between distress and relative indifference in tone.