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

When working with secrets, is it by design that if you use `export const myOutput = myConfig.get("secretProperty")` that the output isn't a secret? The behavior is strange since when you run the program it seems looks like it is a secret, but when you do `pulumi stack output` it isn't. If I use `getSecret` it works as intended. Why do we need both `get` and `getSecret`? I would be more than happy if pulumi just dealt with it so I don't have to think about if it is a secret or not when working with it .

no, this sounds like a bug, could you file an issue with a repro

<@UCWG26BH7> <https://github.com/pulumi/pulumi/issues/8503>

I don't _think_ this is a bug and that for it to be treated as a secret you need to use `getSecret`. It's documented over in the <https://www.pulumi.com/docs/intro/concepts/secrets/#:~:text=By%20reading%20a%20secret%20from%20configuration%20using%20Config.get_secret%20or%20Config.require_secret.|secrets docs>.  So I think this would be considered an enhancement if you would like the `pulumi just dealt with it so I don't have to think about if it is a secret or not` behavior.