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

yeah, really weird behaviour. connection strings\keys from all the other resources get extracted just fine

This is an artifact of how the Pulumi engine works with regards to Resource Outputs.

The main thing to know is that when referencing outputs from resources, Pulumi will take care of "materializing" them when passed into other Pulumi resources. But when trying to print them or do other things with them you need to "force" this.

That's the very high-level explanation. This is explained in more detail at <https://pulumi.io/reference/programming-model.html#outputs> and specifically the `.apply(...)` method is likely what you want to use in this case.

yeah, thats cool, but like I said, I'm not interested in printing it, i'm passing it to a configmap resource in k8s, all the other resources get expanded properly, except redis

ah, ic, so its behaving like this, because even though I'm using it inside the resource you need to use the apply thing to transform it, because all the others do not need transforming. geesh