You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refs #16: Global property section and property to retain functions
You can now apply global properties by adding the `lambdaAtEdge` property to your `custom` section of your `serverless.yml`. **Note:** This section currently only supports the follow option:
* **`retain`** (optional): a boolean, default is `false`, which
sets the DeletionPolicy of the function resource to `Retain`. Can be
used to avoid the currently inevitable CloudFormation stack deletion failure. There are at least two schools of though on how to handle this issue. Hopefully AWS will have this fixed soon. Use at your own discretion.
feat(deletionPolicy): Add deletionPolicy setting
fix(readme): Correct deletionPolicy replication del time
fix(nit): Fix spacing nits
fix(global): add function to global location
Copy file name to clipboardExpand all lines: README.md
+13Lines changed: 13 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,12 @@ objects, the objects all have the same fields, each of which is explained here:
72
72
with a specific cache behavior. If the path pattern is not defined here, the function
73
73
will be associated with the default cache behavior for the specified distribution.
74
74
75
+
You can also apply global properties by adding the `lambdaAtEdge` property to your `custom` section of your `serverless.yml`. **Note:** This section currently only supports the follow option:
76
+
77
+
* **`retain`** (optional): a boolean, default is `false`, which
78
+
sets the [DeletionPolicy][DeletionPolicy] of the function resource to `Retain`. Can be
79
+
used to avoid the currently inevitable [CloudFormation stack deletion failure][ReplicaDeleteFail]. There are at least [two schools of though][HandlingCFNFailure] on how to handle this issue. Hopefully AWS will have this fixed soon. Use at your own discretion.
0 commit comments