helpful-knife-18557
02/13/2023, 3:34 PMmillions-furniture-75402
02/13/2023, 3:46 PMhelpful-knife-18557
02/13/2023, 4:06 PMpulumi.export("myBucket", a_bucket)
and then import that into another stack as a aws.s3.Bucket so I can use the object in the creation of other resourcemillions-furniture-75402
02/13/2023, 4:10 PMconst sharedStack = new pulumi.StackReference("my/stack/reference");
const logBucketId = sharedStack.getOutput("logBucketId");
const logBucket = aws.s3.Bucket.get("log-bucket", logBucketId)
helpful-knife-18557
02/13/2023, 4:18 PMget
feature of CustomResource, by only exporting the minimum info for a remote lookup, but given that one deals in Output
and the get
seems to be "right now" I seem to have hit a bit of a wallmillions-furniture-75402
02/13/2023, 4:20 PMhelpful-knife-18557
02/13/2023, 4:21 PMmillions-furniture-75402
02/13/2023, 4:23 PMhelpful-knife-18557
02/13/2023, 4:24 PMmillions-furniture-75402
02/13/2023, 4:25 PMhelpful-knife-18557
02/13/2023, 4:31 PMHere's a blog post about the concept at a high-level.upon closer inspection, I am doing a version of this, but mostly for already constructed Resource to keep import and export as programmatic as I can (no hard-coded resource name or offband knowledge) to use resource from another stack as information.