- This guide assumes the plugin is deployed and configured. Use the README.md to deploy the plugin
- Note that configuration of the plugin should be done for deck and orca.
- Separately configuration of clouddriver should be done to enable lambda (functions).
- AWS Lambda functions must be enabled in your spinnaker environment and for all required AWS accounts.
This plugin provides 4 stages for spinnaker
- Lambda Deployment
- Lambda Deletion
- Lambda Traffic Management
- Lambda Invocation
- Use this to create/update lambda
- If lambda exists, it is updated, otherwise a new lambda is created.
- It is also possible to create the lambda outside of spinnaker and use this stage only for updating code or specific configuration.
- Use this to delete specific versions of the lambda or the lambda itself.
- You can also use this stage to manage how many older versions of the lambda you want to keep
After lambda is created use this to direct traffic to lambda.
- Simple Deployment: Create an alias and point the version at this lambda
- Weighted Deployment: Create an alias and point the alias at upto 2 versions of the lambda
- Blue/Green Deployment: Invoke the lambda and
- Use this stage to invoke lambda multiple times and capture output
- This stage can be used to generate traffic and logs after a new version of lambda is deployed
- It can be part of a canary analysis where further stages can be used to analyse traffic and make decisions on updating traffic.
- So a lambda deployment pipeline would involve:
- Deployment stage to create/update lambda based on github commits/ cron jobs etc.
- Inocation stage to call the newly created version and invoke the lambda multiple times, generating traffic.
- Canary analysis stage (not part of this plugin) to analyse traffic
- Traffic management stage to update an alias to this new version if canary succeeds.
- Or a delete stage to delete the newly created version if the canary fails.
- Coming soon...
-
The following guides provide examples of plugin development: