feat: allow configuration of SnapStart in properties of AWS Lambda Fu…

[debae]

Adds the possibility to configure the newly added SnapStart property on an AWS Lambda Function.
More info about this can be found : https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html

Closes: #11572

[medikoo]

@debae great thanks for the update. Can we also have some test that covers this functionality?

[medikoo]

@debae great thanks for update. We're getting close!

[debae]

@medikoo All comments have been tackled

[medikoo]

@debae Can you confirm what happens if we first deploy with snapStart: true and then redeploy with this setting removed?

It's really important to confirm on that, to be sure our implementation is solid. Thank you!

[debae]

@debae Can you confirm what happens if we first deploy with snapStart: true and then redeploy with this setting removed?

It's really important to confirm on that, to be sure our implementation is solid. Thank you!

@medikoo Sorry, overlooked your question. Below you can find that scenario as well, and removing the property acts the same as putting it to false resulting in SnapStart:None

[codecov]

Codecov Report

Base: 85.63% // Head: 85.64% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (14720fc) compared to base (c79737e).
Patch coverage: 94.73% of modified lines in pull request are covered.

❗ Current head 14720fc differs from pull request most recent head f362827. Consider uploading reports for the commit f362827 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #11576   +/-   ##
=======================================
  Coverage   85.63%   85.64%           
=======================================
  Files         314      315    +1     
  Lines       13133    13148   +15     
=======================================
+ Hits        11246    11260   +14     
- Misses       1887     1888    +1     

Impacted Files	Coverage Δ
lib/plugins/aws/provider.js	94.70% <ø> (ø)
lib/plugins/aws/deploy-function.js	96.20% <50.00%> (-0.45%)	⬇️
lib/classes/plugin-manager.js	93.72% <100.00%> (ø)
lib/plugins/aws/invoke-local/index.js	69.87% <100.00%> (ø)
lib/plugins/aws/lib/naming.js	97.43% <100.00%> (+0.02%)	⬆️
lib/plugins/aws/package/compile/functions.js	94.92% <100.00%> (+0.14%)	⬆️
lib/utils/import-esm.js	100.00% <100.00%> (ø)
lib/utils/require-with-import-fallback.js	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[medikoo]

That looks great. Thank you @debae !

[charlie-harvey]

Do I have to do anything special to make sure my PublishedVersion is the one being executed? Or it does it with the alias? Say for SQS?