Currently the handler executed by lifecycled is given the lifecycle event name, instance-id and optionally a time (EC2 Spot Instance).
Adding support for additional arguments will assist with providing more information for the handler and also the execution of scripts in a Windows environment, which can't execute a Powershell script directly as it is not an executable. Instead by making the handler Powershell, you can provide a script location as an additional argument which will be invoked.
Currently the handler executed by lifecycled is given the lifecycle event name, instance-id and optionally a time (EC2 Spot Instance).
Adding support for additional arguments will assist with providing more information for the handler and also the execution of scripts in a Windows environment, which can't execute a Powershell script directly as it is not an executable. Instead by making the handler Powershell, you can provide a script location as an additional argument which will be invoked.
Additionally I've updated the README to assist with a Windows example: https://github.com/buildkite/lifecycled/issues/83