This message was deleted.
# awss
sparse-intern-71089
04/12/2021, 9:25 AMThis message was deleted.
e
enough-leather-70274
04/12/2021, 9:29 AMFYI, my code is
Copy code
deploy_bucket = aws.s3.Bucket(
"my-bucket",
)
deploy_object = aws.s3.BucketObject(
"archive",
key="app.zip",
bucket=deploy_bucket.id,
source=AssetArchive({"app": FileArchive(str(some_path.resolve()))}),
)
lambda_fn = aws.lambda_.Function(
"lambda-fn",
role=execution_role.arn,
s3_bucket=deploy_bucket.id,
s3_key=deploy_object.key,
s3_object_version=deploy_object.version_id,
handler="app.main.handler",
runtime="python3.8",
)enough-leather-70274
04/12/2021, 9:37 AMAlso, for clarify, preview appears to recognise the bucket object has changed and the lambda needs an update, but the actual deployment doesn't update the lambda:
Copy code
(venv) % pulumi up
Previewing update (<redacted>/dev)
View Live: <redacted>
Type Name Plan Info
pulumi:pulumi:Stack <redacted>
├─ aws:s3:Bucket my-bucket
~ │ └─ aws:s3:BucketObject archive update [diff: ~source]
└─ aws:iam:Role lambda-iam-role
~ └─ aws:lambda:Function lambda-fn update [diff: +s3ObjectVersion]
Resources:
~ 2 to update
8 unchanged
Do you want to perform this update? yes
Updating (<redacted>/dev)
View Live: <redacted>
Type Name Status Info
pulumi:pulumi:Stack <redacted>
└─ aws:s3:Bucket my-bucket
~ └─ aws:s3:BucketObject archive updated [diff: ~source]
Outputs:
base_url: <redacted>
Resources:
~ 1 updated
9 unchanged
Duration: 12sb
brave-planet-10645
04/12/2021, 9:39 AMJust out of question, why are you pushing the code to S3 instead of letting Pulumi push it to the lambda?
e
enough-leather-70274
04/12/2021, 9:40 AMbecause it's too big
b
brave-planet-10645
04/12/2021, 9:41 AMAh ok. So what you'll need to do is have another lambda that listens to an event on that bucket and updates the lambda when new code is pushed. The SDK has a function for this: https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Lambda.html#updateFunctionCode-property
e
enough-leather-70274
04/12/2021, 9:43 AMbugger
enough-leather-70274
04/12/2021, 9:43 AMok, ta
b
brave-planet-10645
04/12/2021, 9:44 AMHow come it's so large? Would it be possible to split it out? Another option could be to use a container to run your lambda instead?
e
enough-leather-70274
04/12/2021, 9:47 AMyeah, that's defo another option worth exploring. In real life we also get both the function and the layers provided to us as a zip, hence why we're looking at s3
enough-leather-70274
04/12/2021, 9:48 AMWhy doesn't pulumi just re-up the lambda when we update the object version tho?
b
brave-planet-10645
04/12/2021, 10:15 AMBecause you haven't technically updated the lambda. You've updated the S3 bucket object
brave-planet-10645
04/12/2021, 10:18 AMExample: if you use the "upload from" button on the lambda page, it goes off to s3, grabs the files and updates the lamdba. If you then update the code in the S3 bucket, you have to go back to lambda in the console and re-run the "upload from" process
e
enough-leather-70274
04/12/2021, 11:15 AMWell yes - that’s what pulumi should do
enough-leather-70274
04/12/2021, 11:16 AMAnd indeed the preview process indicates it will
enough-leather-70274
04/12/2021, 11:16 AMIt just doesn’t do that when you execute the change.
enough-leather-70274
04/12/2021, 11:19 AMPulumi knows the bucket object has been versioned, and knows about the dependency of the lambda on that version as its being passed in explicitly
enough-leather-70274
04/12/2021, 11:19 AMI guess what I’m saying is this feels like a bug rather that working as designed
b
brave-planet-10645
04/12/2021, 12:09 PMLet me look into this a bit further
brave-planet-10645
04/12/2021, 12:33 PM@enough-leather-70274 I've realised what is wrong... you haven't turned on versioning on your s3 bucket. It should look like this:
Copy code
deploy_bucket = aws.s3.Bucket(
"my-bucket",
versioning=aws.s3.BucketVersioningArgs(
enabled=True,
)
)brave-planet-10645
04/12/2021, 12:33 PMYou've got the versioning set up correctly on the lambda, but the version id will never change
14 Views