Lee Zen

@pbzdyl For now, you wrap the promise with `pulumi.secret` to ensure it gets marked as secret.

We definitely want to get the `type` and `id` fields into the docs instead of having you need to hunt for them yourself. For now, I'll describe some steps below...

Could you please clarify what you're trying to do? `crd2pulumi` generates a package on your behalf, which will have its own `package.json` and this is what `utilities.{ts,js}` refers to. You...

Looking at this further, it's awkward since the `package.json` generated by `crd2pulumi` doesn't actually have the right version information in it, so it's not really "ready" to be used out...

I was able to repro this. Oddly enough, the dashboard shows up as a resource within the resource group, but navigating the dashboard produces the error as described above.

Wouldn't these values be ephemeral and not something you'd configure as part of your infrastructure? Could you please describe a bit more about your use case?

Are you looking for https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ecs/#TaskDefinition-run or do you mean something else?

Sorry, I thought I had replied but somehow I must not have hit 'Comment'. The `run` needs to happen in a context not within the program execution itself. Typically, we...

In addition to this, we should be consistent about the type tokens for resources as there are some that are `awsx:x:...` while others are `awsx:...` or even `aws:...`

Crosswalk (`awsx`) uses `@pulumi/aws` which uses `terraform-provider-aws` In this particular case, an 'import' isn't actually an import, but a read, which ends up invoking the `get`: https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/ec2/vpc.ts#L77 In the case...