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

Maybe what I'm asking (in general) is:

_How to access a dependent auto-created sub-resource?_

I suppose there is a way to traverse the state DAG programmatically? The only examples I've seen so far were to access the state of explicitly defined resources, for which I have a direct programmatic handle on.

Looks like <https://www.pulumi.com/docs/intro/concepts/resources/#resource-get> could be used to read state, but shouldn't Pulumi already be aware of the child secret resource?

or do I need to first <https://www.pulumi.com/docs/intro/concepts/resources/#import> so I can get a programmatic handle on the child-resource? (this approach looks redundant, as Pulumi is probably already aware of the secret)

Is the secret created in pulumi? You should be able to export it explicitly. You will need to pass the `--show-secrets` to show the secret when you do a `pulumi stack output` .