...
Input Name | Input Code | Type | Required | Description |
Additional Arguments | FDAWS_LAMBDA_INP_ADD_ENV_VAR_ADDITIONAL_ARG | String | No | Literal key and value pairs. e.g. --region=us-east-1 And for boolean type arguments give the option without any value. e.g --publish --debug |
Environment Variables | FDAWS_LAMBDA_INP_ENV_VAR | String | No | Environment Variables in acceptable format. |
Publish new version | FDAWS_LAMBDA_INP_PUBLISH_VERSION | Boolean | No | Select to publish a new version. Default value is false. |
Step-ii: getLambdaAlias
This step will get Lambda Alias detail and set Lambda Alias current version in output, which we will use in upsert lambda operation.
...
Step-iii: upsertLambdaAlias
This step will update the given Alias ( Dev Prod ) , with the newly published version and configured the additional argument with routing config information.
...
In above configuration using following Inputs.
...
We have one Alias name as Prod and which is currently pointing to the function version 18 ( Blue deployment ), and 100% traffic is shift to this function version.
...
Once the deploy execution completed we can see that new function version is published and 20% of traffic will shift to this newly published version 19 21 ( Green deployment ) and remaining 80% will shift to old, stable version 18 20 . ( Blue deployment ).
...