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

I think you are looking for structured config:
<https://www.pulumi.com/docs/intro/concepts/config/#structured-configuration>

I'm trying to get away from structured config because I've found that it's a mess when dealing with data structures containing both secret and non-secret values

<https://pulumi-community.slack.com/archives/C84L4E3N1/p1653095609591829>

Ah yeah, so  if not using structured config, then the pattern is to prefix each config variable with the namespace.
<https://www.pulumi.com/docs/intro/concepts/config/#configuration-keys>

Do you have any experience dealing with structured config where some values are secret and some arent?

Unfortunately, I have not dug into that use-case.