This message was deleted.

actually, i think the cycle is even simpler than that - i’ve got some lambda f that calls newContext and newContext is defined as

let newContext;

and then at the bottom fo the file

newContext = ...

where … includes some code that needs the arn of the lambda f

hmm, cc @bitter-oil-46081?

I am not really sure how to make that work. If I am understanding correctly, logically you want to end up with the source code for a lambda to end up capturing the arn that lambda is created with? Do you expect when you capture

newContext

you see the value that you end up defining later in the file? I think that the pattern of doing a let to initialize a variable, capturing that, and then latter assigning to it in the deployment program is going to lead to racy behavior since you don't have control over when the lambda which captured newContext is serialized.