Update active-versions.md

This commit is contained in:
Alex Gaesser 2018-02-02 10:49:54 -08:00 committed by GitHub
parent eea117660b
commit b53de29cd1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -20,7 +20,7 @@ The 'Latest' version refers to the most recent version created by the last updat
*Please note: the 'Latest' tag will point to a different version number each and every time you update your function.*
Default configuration for activeVersions when a new function is created:
```yml
```
"activeVersions": [
{
"version": "$LATEST",
@ -35,7 +35,7 @@ The 'Active' version can point to more than one version of your function, includ
For example, say you wanted to test a new version of your function to determine if it was production-ready. You could specify that 10% of the traffic be routed to that new version, and route the remaining 90% to the stable version. You can gradually route more traffic to the new version as you become more confident in its performance.
### Examples
```yml
```
"activeVersions": [
{
"version": "$LATEST",
@ -46,10 +46,10 @@ For example, say you wanted to test a new version of your function to determine
100% of traffic will go to the most recently published update.
```yml
```
"activeVersions": [
{
"version": "$LATEST",
{
"version": "$LATEST",
"percentage": 80.0
},
{
@ -60,7 +60,7 @@ For example, say you wanted to test a new version of your function to determine
```
80% of traffic goes to the most recently published update, and 20% goes to version 2.
```yml
```
"activeVersions": [
{
"version": "5",
@ -86,7 +86,7 @@ You can configure active versions in the serverless.yml file, but you can also u
3. Select 'Configure Active Version'
- API: (update function)
```yml
```
"activeVersions": [
{
"version": "$LATEST",