https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
e
FYI, 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",
)
Also, 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: 12s
b
Just out of question, why are you pushing the code to S3 instead of letting Pulumi push it to the lambda?
e
because it's too big
b
Ah 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
bugger
ok, ta
b
How 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
yeah, 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
Why doesn't pulumi just re-up the lambda when we update the object version tho?
b
Because you haven't technically updated the lambda. You've updated the S3 bucket object
Example: 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
Well yes - that’s what pulumi should do
And indeed the preview process indicates it will
It just doesn’t do that when you execute the change.
Pulumi knows the bucket object has been versioned, and knows about the dependency of the lambda on that version as its being passed in explicitly
I guess what I’m saying is this feels like a bug rather that working as designed
b
Let me look into this a bit further
@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,
    )
)
You've got the versioning set up correctly on the lambda, but the version id will never change
13 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by