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

image.png

I believe you have to use the CLI to see it.

For that one it’d be `pulumi config get data --show-secrets` to see it in plain text. See <https://www.pulumi.com/docs/reference/cli/pulumi_config/> and <https://www.pulumi.com/docs/reference/cli/pulumi_config_get/>

``` pulumi config get data --show-secrets
Error: unknown flag: --show-secrets
Usage:
  pulumi config get &lt;key&gt; [flags]

Flags:
  -h, --help   help for get
  -j, --json   Emit output as JSON
      --path   The key contains a path to a property in a map or list to get

Global Flags:
      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
      --config-file string           Use the configuration values in the specified file rather than detecting the file name
  -C, --cwd string                   Run pulumi as if it had been started in another directory
      --disable-integrity-checking   Disable integrity checking of checkpoint files
  -e, --emoji                        Enable emojis in the output
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --non-interactive              Disable interactive mode for all commands
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
  -s, --stack string                 The name of the stack to operate on. Defaults to the current stack
      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything &gt;3 is very verbose

An error occurred: unknown flag: --show-secrets```
Actually it looks like --show-secrets exists on `pulumi config` but not on `pulumi config get` . Which also seems to be the case in the linked docs.

`pulumi config get` automatically unwraps secrets into plaintext, but `pulumi config` will mask secrets unless `--show-secrets` is passed.

Cheers... although given Roderik was asking about an `output` wouldn't he need `pulumi stack output --show-secrets data` ?

Heh I think we’ve strayed quite far from what I think Roderik was originally asking which was “Can I see the value in the console?”

Haha, thanks for the clarity. I was thinking `get` inherited all the flags from the parent `config`. <@U01LC6520KW>, I thought that initially about the outputs but in the Pulumi console on the web the outputs aren’t shown in the UI like the screenshot.