Open away168 opened 3 years ago
I'll add that to github, but the gist of it is this:
Simple deployment: You choose a single version and the plugin directs all traffic to this version
Weighted deployment: You choose 2 versions and the way to split traffic between the two (say 10 percent to the newest just deployed version and 90 percent to the previous version)
Blue/Green : You choose a health check type - (currently only a lambda invocation health check is provided) and a version to deploy. Health check is run against this version, if the health check passes, all traffic to this lambda is pointed at the chosen version. If the health check fails, then no change is made to the lambda traffic allotment
There is also a separate stage called the Invoke stage. This does not manage traffic but can be used as a building block for some canary analysis before deploying your lambda. This stage simply invokes a specific version of the lambda with the given payload. A subsequent stage (not part of this plugin) can be used to analyze cloudwatch or other logs and decide if the (new) version is functional enough, and if so, a deployment stage (using simple deployment abaove) can be used to direct all traffic to the new version.
please provide some documentation on how the Blue/Green and weighted route stage works.