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

Hi, is there any reason why `yaml.ConfigGroup` `yaml` field does not accept `Pulumi.Input&lt;string&gt;` ? This way I'm unable to pass a string created from an output, for example from a secret

you can always pulumi.output(myinput).apply(yaml =&gt; {}) though

not recommended to create resources inside apply, because unable to see them during preview, they're not part of the dependency graph

if it's not by design works this way, then should be fixed

I think the reason it does not currently accept Input is actually the same one you point out - it can’t know what actual resources to create until the yaml is available - and if it accepted input it would have to do the same “create resources inside apply” in its implementation. 