High level summary / overview of the feature request
As a user of the Lambda plugin, I would like the Lambda Deploy stage to keep only a certain amount of Lambda versions when deploying.
The functionality should mimic that of EC2 and ECS deployments, where you can specify the amount of server groups to keep.
It has been observed in our environment that the number of versions kept impacts the performance of the Lambda Deploy stage - the more versions, the slower the Lambda Deploy stage is. (Guessing due to cache and iteration over versions).
Details of the environment.
What is the version of the plugin?
1.0.8
What is the version of spinnaker?
1.26
Current behavior
Currently the Lambda Deploy stage provides no option of specifying the amount of versions to keep. If the Lambda Deploy stage is has version publishing enabled, it will forever keep creating new versions without cleaning up the old ones.
Expected behavior (Detailed description of the expected behavior and how it is different from the current behavior).
I expect the Lambda Deploy stage to have an option to keep N of the latest versions and delete the rest. Much like the EC2/ECS deploy stages do with server groups - see screenshot:
As a user of the Lambda plugin, I would like the Lambda Deploy stage to keep only a certain amount of Lambda versions when deploying.
The functionality should mimic that of EC2 and ECS deployments, where you can specify the amount of server groups to keep.
It has been observed in our environment that the number of versions kept impacts the performance of the Lambda Deploy stage - the more versions, the slower the Lambda Deploy stage is. (Guessing due to cache and iteration over versions).
Currently the Lambda Deploy stage provides no option of specifying the amount of versions to keep. If the Lambda Deploy stage is has version publishing enabled, it will forever keep creating new versions without cleaning up the old ones.
I expect the Lambda Deploy stage to have an option to keep N of the latest versions and delete the rest. Much like the EC2/ECS deploy stages do with server groups - see screenshot: