What does a AWS::Serverless::Function DeploymentPreference Type of AllAtOnce actually do?

When using an AWS SAM template to define an AWS::Serverless::Function, what practical difference is there between not specifying a DeploymentPreference property and specifying one with a Type of AllAtOnce?

With this minimal configuration (no Alarms or Hooks specified), is the end result somewhat identical in that the new version is immediately published? Presumably the CodeDeploy version creates an alias as well, but are there any other differences to be aware of?

主題

無伺服器運算開發人員工具管理與治理

標籤

無伺服器 AWS Lambda AWS CodeDeploy AWS CloudFormation

語言

English

rePost-User-6116601

已提問 1 年前檢視次數 216 次

1 個回答

最新
最多得票
最多評論

這些答案是否有幫助？支持正確答案，以幫助社區從您的知識中受益。

This page explains the different deployment options - https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/automating-updates-to-serverless-apps.html

專家

Indranil Banerjee AWS

已回答 1 年前

rePost-User-6116601
1 年前
Thank you, I have already read that and all other documentation I can find on the subject. Unless I'm missing something really obvious, I can't see that it answers my question.

Specifcally, I note that adding AutoPublishAlias alone will create an alias on the Lambda function. What difference does adding a DeploymentPreference with Type AllAtOnce make compared to not adding it at all (other than the obvious that it creates CodeDeploy resources - but what effect does that actually have)?

What does a AWS::Serverless::Function DeploymentPreference Type of AllAtOnce actually do?

相關內容