No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

If `Output ` is not dealt properly in before serialization. The resulting string has this writing instead of value:
```Calling [toString] on an [Output&lt;T&gt;] is not supported.\n\nTo get the value of an Output&lt;T&gt; as an Output&lt;string&gt; consider either:\n1: o.apply(v =&gt; `prefix${v}suffix`)\n2: pulumi.interpolate `prefix${v}suffix`\n\nSee <https://www.pulumi.com/docs/concepts/inputs-outputs> for more details.\nThis function may throw in a future version of @pulumi/pulumi```
Why is there not at least and error logged out that something like this happened? I can imagine string like this shipped into the resulting infrastructure without any notice (if you not examining the outputs thoroughly).

It's not the default currently. You can have this behavior via setting `PULUMI_ERROR_OUTPUT_STRING` env var thanks to <https://github.com/pulumi/pulumi/pull/14811>

see <https://www.pulumi.com/docs/iac/cli/environment-variables/> for a full list