This message was deleted.
# generals
sparse-intern-71089
10/04/2018, 8:16 PMThis message was deleted.
c
creamy-potato-29402
10/04/2018, 9:00 PM@faint-application-2746 that is on purpose
creamy-potato-29402
10/04/2018, 9:00 PMyou mean the name, right?
creamy-potato-29402
10/04/2018, 9:00 PMThe name gets an auto-suffix so that you can deploy your app multiple times.
creamy-potato-29402
10/04/2018, 9:01 PMAlso so that there aren’t name collisions generally.
f
faint-application-2746
10/04/2018, 9:21 PMYeah, I understand that but sometimes a S3 bucket is fixed as name as other things write to it and it might even have pre-existing data
faint-application-2746
10/04/2018, 9:21 PMsame behaviour is in serverless framework but they have serverless-plugin-existing-s3 to deal with that
b
bitter-oil-46081
10/04/2018, 9:31 PMI think if you want to use an existing S3 bucket, you can't use the cloud abstraction directly, today. You could use the get method on aws.s3.Bucket to retrieve an existing bucket, but you would unfortunately not get the nice
on*cloud.Bucketl
lemon-spoon-91807
10/04/2018, 9:34 PMHere's how it will work RSN (i believe when our next release is)
lemon-spoon-91807
10/04/2018, 9:34 PM1. You'll include
import * as aws from "@pulumi/aws"lemon-spoon-91807
10/04/2018, 9:34 PM2.
const bucket = aws.s3.Bucket.get("yourbucketid")❤️ 1
lemon-spoon-91807
10/04/2018, 9:35 PMThat will give you the real bucket resource.
lemon-spoon-91807
10/04/2018, 9:35 PMif you want to do things like listen for events, you can do:
bucket.onObjectCreated(...)👍🏻 1