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 have to wrap all the properties you need which are outputs inside of a `pulumi.all`

```
const gcpCredentials = new k8s.core.v1.Secret('gcp-credentials', {
  metadata: {
    namespace: namespace.metadata.name,
    labels: config.appLabels
  },
  type: 'Opaque',
  stringData: {
    'gcp-credentials.json': serviceAccount.key.privateKey.apply(x =&gt; Buffer.from(x, 'base64').toString('utf8'))
  }
});
```

that is just a key, not the whole json, right?

It’s the entire GOOGLE_APPLICATION_CREDENTIALS file

So we mount this secret in our pods, and use an env `GOOGLE_APPLICATION_CREDENTIALS` as a path to the mount.

<@UD2HJDBCL>, if I set whole resource as stack output, it comes back as a plain JSON , so they already have a generic code which does all the promise resolution, I'll try to find it

<@UGDSK5RNC>, thanks, I'll check, but I recall there were problems with GOOGLE_APPLICATION_CREDENTIALS in  a ruby library project is using

I was looking at .priavateKey in the stack output and though it is a whole .Key . got confused by the fact that inside that privateKey there is another `private_key`