Skip to content

Commit

Permalink
Adding ToC to docs
Browse files Browse the repository at this point in the history
  • Loading branch information
sanathkr committed Nov 29, 2017
1 parent f7af65a commit c686949
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/globals.rst
@@ -1,6 +1,8 @@
Globals Section
===============

.. contents::

Lambda functions within a SAM template tend to have shared configuration such as Runtime, Memory,
VPC Settings, Environment Variables etc. Instead of duplicating this information in every function, you can
write them once in the ``Globals`` section and let all Functions inhert it.
Expand Down
2 changes: 2 additions & 0 deletions docs/safe_lambda_deployments.rst
@@ -1,6 +1,8 @@
Safe Lambda deployments
=======================

.. contents::

Pushing to production can be nerve-racking even if you have 100% unit test coverage and state-of-art full CD system.
It is a good practice to expose your new code to a small percentage of production traffic, run tests, watch for alarms
and dial up traffic as you gain more confidence. The goal is to minimize production impact as much as possible.
Expand Down

1 comment on commit c686949

@icast7
Copy link
Contributor

@icast7 icast7 commented on c686949 Jan 25, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where can I find more info about the rules for deciding whether the canary deployment can complete successfully? Looking at doing something like this (https://aws.amazon.com/blogs/compute/implementing-canary-deployments-of-aws-lambda-functions-with-alias-traffic-shifting/) using SAM instead of Step Functions. Thanks!

Please sign in to comment.