More precisely, it's already an

Input<T>

, as

Input<T>

is defined as the union of

T | Input<T> | Output<T>

i.e. this would be nice:

const clusterResult = gcp.container.getCluster({name: 'my-custer'})

new my.Resource('foo', {
  clusterEndPoint: clusterResult.endpoint
})

if

clusterResult

would be a regular pulumi resource i could tap into the subproperties without unwrapping.

but since it’s a

Promise

I first would have to unwrap it via

.then

in order to get a subproperty.

somehow I can’t get .get to work though 😕

I created a small example

creates a GCS bucket via

gsutil mb <gs://pulumi-experiment-bucket>

now I’m trying to use that bucket in pulumi via

import * as gcp from '@pulumi/gcp';

const myBucket = gcp.storage.Bucket.get('my-bucket', 'pulumi-experiment-bucket');

but I’m getting this error:

Previewing changes:

     Type                   Name                                            Plan       Info
 +   pulumi:pulumi:Stack    pulumi-query-experiments-christian-experiments  create
 >-  └─ gcp:storage:Bucket  my-bucket                                       read       1 error

Diagnostics:
  gcp:storage:Bucket: my-bucket
    error: Preview failed: refreshing urn:pulumi:christian-experiments::pulumi-query-experiments::gcp:storage/bucket:Bucket::my-bucket: Error reading Storage Bucket "": googleapi: Error 400: Required parameter: project, required

error: an error occurred while advancing the preview

Note I already set the project in the provider config via

pulumi config set gcp:project my-project

ok actually I got it working now by changing it to

import * as gcp from '@pulumi/gcp';

const myBucket = gcp.storage.Bucket.get(
  'my-bucket',
  'pulumi-experiment-bucket',
  { project: 'my-project', name: 'pulumi-experiment-bucket' }
);

In this case, the project

So I’m wondering why I have to specify the bucket name twice (once as second param, and once as property

name

to the third param)?

Well at least in GCP I think the bucket name IS the id.

There’s no random uuid or so assigned to a bucket.

Hmm, so I now changed the ID param to something other than

name

and now pulumi fails with:

Previewing changes:

     Type                   Name                                            Plan       Info
 +   pulumi:pulumi:Stack    pulumi-query-experiments-christian-experiments  create
 >-  └─ gcp:storage:Bucket  my-bucket                                       read       1 error

Diagnostics:
  gcp:storage:Bucket: my-bucket
    error: Preview failed: reading resource urn:pulumi:christian-experiments::pulumi-query-experiments::gcp:storage/bucket:Bucket::my-bucket yielded an unexpected ID;expected pulumi-experiment-bucket-foo, got pulumi-experiment-bucket

error: an error occurred while advancing the preview

So it seems pulumi uses indeed the

name

property for the lookup but then tries to match that name with the manually provided

id

and complains if they don’t match.

@microscopic-florist-22719 might know more about this behavior

And as far as I can see it this problem applies to a lot of GCP resources. GCP uses deterministic / named IDs for most of the resources (compared to AWS which often has a random ID and a separate name property for their resources).

This seems like it could be a tricky integration issue with the GCP Terraform provider, which is what our Pulumi GCP provider is derived from

Can you file an issue in https://github.com/pulumi/pulumi-gcp describing what you're seeing? This is definitely something I'd like to investigate further.