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

Reading it to what? Do you mean, building up a map of nested key:value pairs?

Indeed. That seems the more reasonable option that pre-defining a rigid struct with all the duplicate declarations that entails.

More like a normal JSON or YAML key:value tree.

pulumi.Config gives you that out of the box. Can you pass the entire object around and use it as-is?

My overall goal is to pass all the Config values into Dockerfile via ARG+ENV without naming every individual key.  Do you have a way?

To answer your question, no I can't use the Config object as is.  The config data needs to leave Pulumi as text.

I believe I did something like that a while ago, then replaced it with simpler code. I'll have a quick hunt through old commits...

```const config = pulumi.runtime.allConfig();
for (let kv in config) {
  <http://pulumi.log.info|pulumi.log.info>(`I see ${kv}: ${config[kv]}`);
}```

WORKS! Even the secrets make it all the way thru to Docker.  Thanks again!