From de1ec652fc7f9b87f1c491894b9c0d91ceb00556 Mon Sep 17 00:00:00 2001 From: Jeff McLean Date: Thu, 19 Sep 2019 11:32:41 -0500 Subject: [PATCH] Update README to better explain default --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ff00eee..8ec6ee9 100644 --- a/README.md +++ b/README.md @@ -70,7 +70,7 @@ See the `alias remove` command below. ## Maintain versions -By default, when you deploy, the version of the function gets assigned the retention policy of 'Delete'. This means any subsequent deploys will delete any version without an alias. This was done because you can no longer tell which alias it came from. +By default, when you deploy, the version of the function gets assigned the retention policy of 'Delete'. This means any subsequent deploys will delete any version without an alias. This was done because each lambda version has its own stack. That stack can contain differences in not only the function code, but resources and events. When an alias is removed from a version and the version of the lambda is not deleted, it is no longer possible to tell which stack it came from and which resources/events it was meant to work with. Therefore versions without aliases will get deleted on subsequent deploys. There are usecases where retaining versions is less risky and as such, you can opt into retaining these versions by deploying with the `--retain` flag.