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

If you use `requireObject` instead of `requireSecretObject` it will use the plaintext version. But note that it will be saved to pulumi state as plaintext.

I have already tried this and it does not work

I have also tried `pulumi.unsecure` but it does not work either

Note that it works fine in the CLI `pulumi config --show-secrets` so it is not a stack bad configuration

Hmm... maybe it's because the whole object is not a secret but the individual keys are?

It gives me this:
```"[{\"pass\":\"[secret]\",\"user\":\"admin\"},{\"pass\":\"[secret]\",\"user\":\"admin2\"}]"```

yeah I think it's probably a bug - but I do think it's related to the fact that the individual keys are secrets rather than the entire object which means that `unsecret` or `requireObject` don't unsecret the top-level object because it was never a secret in the first place.

What it should do is also unsecret the individual keys.. but it seems it is not doing that.

Yep, I might look into contributing tomorrow

But it seems pretty complicated for what I have seen so far