This message was deleted.
# generals
sparse-intern-71089
09/25/2020, 9:53 PMThis message was deleted.
w
white-balloon-205
09/25/2020, 10:15 PM
Hey Ala - great to hear from you!
That is certainly surprising. Between two of these updates - does the code uploaded to one of the Lambda's actually change?
It sounds like this may be an issue in the diff logic on the archive used for the Lambda - and could plauibly be related to WSL2. Any chance you can confirm whether you see the same thing in a Linux environment?
A GitHub issue with any additional details you could share would definitely be helpful.
c
chilly-magazine-6129
09/26/2020, 1:01 AMSame here @white-balloon-205, phenomenal work on Pulumi. And no, the code doesn't change - I'm purposefully and immediately only editing the memory part of the plan (using pico), and pulumi upping. I'll try out a linux VM to validate if this happens there. I tried pulling the source from git again, dos2unix the entire folder. quite unusual
chilly-magazine-6129
09/26/2020, 1:09 AM@white-balloon-205 I think I figured it out. We apparently introduced an unexpected string into the plan because of a templating default:
chilly-magazine-6129
09/26/2020, 1:09 AMI suspect that's what caused the issue
w
white-balloon-205
09/28/2020, 10:47 PM
Ahh - interesting! I would have actually expected that to be an error - honestly not sure what happens if you include the empty string in
extraIncludePaths2 Views