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

What do you mean when you say that none of those properties are available?  

It should be the case that you see a Bucket object returned from:

export const bucket = page.bucket;

for example `export const arn = page.bucket.arn` will say arn doesn't exist on output instance and if I use apply `page.bucket.apply(bucket =&gt; bucket.arn)` arn is empty....for me the only way it works is if I do `export const bucketId = page.bucket` bucketId ends up being just a string

I was returning a load balancer resource to my client code and hoping I could just do lb.dns_name which set me down this path of trying to understand more.   I could return the dns_name as a string and access from my construct but returning a resource like they did in the example just doesn't yield what I expect so figured my expectation must be wrong.

That would indicate something is not working correctly. You should get a Bucket instance here. 

Is it possible you are running into the same thing mentioned at <https://github.com/pulumi/pulumi-awsx/issues/972#issuecomment-1376033119|https://github.com/pulumi/pulumi-awsx/issues/972#issuecomment-1376033119>?  The steps suggested there might help your case as well?

That does look awfully similar.  Let me try it out.  Awesome.

Hi <@UB3BGTV63>, so that didn't work for me and I have been exploring more.  Noticed someone posted, <https://github.com/pulumi/pulumi-component-provider-ts-boilerplate/issues/34> ,  the same in boilerplate-ts thought you may have some ideas.   I was trying with different versions of clients and ts/python to see if behavior was ever different but so far that bucket is always a string specifically the id.   Thank you again for help.