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

the actual bucket (export const adminBucket = new aws.s3.Bucket) from our core infra config

I could add an export for adminBucket.id and forward that?

what’s its value? it seems to be the wrong type. I would export const config.adminBucket first to see what the value is set to

```  pulumi:pulumi:Stack (admin-dev):
    OutputImpl {
      __pulumiOutput: true,
      resources: [Function (anonymous)],
      allResources: [Function (anonymous)],
      isKnown: Promise { &lt;pending&gt; },
      isSecret: Promise { &lt;pending&gt; },
      promise: [Function (anonymous)],
      toString: [Function (anonymous)],
      toJSON: [Function (anonymous)]
    }```

that’s my console log, it should be a Output&lt;Bucket&gt;

I can try apply and then .id or something too perhaps?

```const updatedFiles: BucketObject[] = [];
config.adminBucket.apply(bucket =&gt; {
  const adminBucketDir = `${__dirname}/../build/`;
  crawlDirectory(adminBucketDir, (filePath: string) =&gt; {
    const relativeFilePath = filePath.replace(adminBucketDir + "/", "");
    console.log(relativeFilePath, filePath);
    const contentFile = new aws.s3.BucketObject(
      relativeFilePath,
      {
        key: relativeFilePath,
        acl: "public-read",
        bucket: bucket.id,
        contentType: mime.getType(filePath) || undefined,
        source: new pulumi.asset.FileAsset(filePath),
      }
    );
    updatedFiles.push(contentFile);
  });
})```
This seems to be successful, I’m going to export the id and see if I *need* to apply

we’re good, I’ll start using `bucket.id` over `bucket` for `new aws.s3.BucketObject` in the future

cheers for the help