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

Or, if you're using TypeScript, you can always do something like

```
let datastore = await vsphere.getDatastore({
  name: "bdf1000-01",
  datacenterId: "datacenter-21"
});

console.log(datastore.id);
```

Not at all :slightly_smiling_face:  We actually have gone round and round on whether we can make these calls synchronous.

It would be a "lie" since they actually do I/O under the hood, so we've presently landed on returning promises.

But appealing from a usability perspective.

I actually suspect that, in the limit, the main conversion challenge from TF to Pulumi will be promises :slightly_smiling_face:

I'm having a bit of trouble understanding how to provide credentials to the provider

(Then again, it is pretty nifty that you can do I/O, have lots of async work in flight, etc, in your cloud infra programs, so...)

The config vars are auto-generated in the `config` module: <https://github.com/Smithx10/pulumi-vsphere/blob/master/sdk/nodejs/config/vars.ts>

Does the func Provider() tfbridge.ProviderInfo { . function

automatically know what to ask for in pulumi config?

when I first went to pulumi up, it prompted for UNs and PW's

So, e.g.

```
$ pulumi config set vsphere:user admin
$ pulumi config set vsphere:password mysecretpassword --secret
```

If you look in the config section, it uses `require` calls for the required configuration variables:

```
export let password: string = __config.require("password");
```

So, it basically knows what to ask for, based on the TF metadata it read to generate the package.

The Terraform Provider also takes EnvVars

You made it very easy to pull in TF hahahaha

&gt; The Terraform Provider also takes EnvVars

Oh, I wonder if you're hitting: <https://github.com/pulumi/pulumi-terraform/issues/181>

For config variables that are required, but take defaults from environment variables, we don't always generate the right thing.

If so, I know <@U84HBHXS8> is actively working on a fix for this that should land next week.