Release v0.9.1

Fixed

• fix(ghes): Corrects preview option #482 @mcaulifn @samuelb

Release v0.9.0

Added

• Add support for GitHub Enterprise Server (GHES) #412, #481, #467 @mcaulifn @jonico
• Allow configuring additional security groups #392 @surminus

Changed

• Log groups per type of logging #476
• Copy directory after installing zip #444 @masterful
• Update ubuntu example with rootless docker and non privileged user #433
• Changed strategy in scaling. Previous the module scaled by checking for any queued workflow for the repo initiation the check_run event. Now the module scales only if the correlated check_run is still in queued state. #423

Fixed

• Fix missing permissions for CloudWatch Agent #445 @bennettp123
• Swap scale up/scale down timeout description #468 @jonico
• Fix for invalid configuration #466 @jonico
• Add ssm:GetParameter to runner-ssm-parameters #446 @bennettp123
• Replace crypto #429
• Scale up lambda deprecated attribute #410

Migrations

Changes related to logging groups introduced via #476 will destroy existing logging group in AWS cloudwatch for runners log. In case you would like to keep the logging ensure you remove the log group from the state before running an apply

export RESOURCE=$(terraform state list | grep "aws_cloudwatch_log_group.runner")
terraform state rm $RESOURCE

Release v0.9.0_next

Pre release 0.9.0

Release v0.8.1

Changed

• Policy is missing for streaming logs to cloudwatch #388

Release v0.8.0

Changed

• Examples upgraded to Terraform 13 (#372)

Added

• Streaming runner logs to cloudwatch #375

Release v0.7.0

Changed

• Small clarifications in the README #368 @lrytz

Added

• Allow operator to pass in a list of managed IAM policy ARNs for the runner role #361 @jpalomaki
• expand options for sourcing lambda to include S3 #292 @eky5006

Release v0.6.0

Added

• Only allow tagging and termination of runner instances #201 @jpalomaki

Fixed

• Fix pagination with listing self-hosted runners #202 @HenryNguyen5

Release v0.5.0

Added

• feat: Manage log groups via module. When upgrading you have to import the log groups by AWS into your state. See below the example commands for the default example.

terraform import module.runners.module.runner_binaries.aws_cloudwatch_log_group.syncer "/aws/lambda/default-syncer"
terraform import module.runners.module.runners.aws_cloudwatch_log_group.scale_up "/aws/lambda/default-scale-up"
terraform import module.runners.module.runners.aws_cloudwatch_log_group.scale_down "/aws/lambda/default-scale-down"
terraform import module.runners.module.webhook.aws_cloudwatch_log_group.webhook "/aws/lambda/default-webhook"

• feat: Added option to binaries syncer to upgrade to pre-releases, preventing any auto-updating on startup. Option runner_allow_prerelease_binaries is disabled by default. (#141, #165) @sjagoe

• feat: SSM policies are by default disabled, set enable_ssm_on_runners to true to enable access to the runner instances via SSM. (#143) @HenryNguyen5

• feat: Log full sqs event (#147) @HenryNguyen5

Release v0.4.0

Added

• Add option to keep runners idle

Release v0.3.0

Added

• feat: Add support for ARM64 runners #102 @bdruth
• feat: added variables in the root module to allow passing in pre and and post install #45 @jaydenrasmussen

Updated

• fix: Build script not entering all the module directories (#103) @alonsohki
• fix: Remove Orphan AWS runners (#79)
• fix: documentation for downloading lambdas (#78) @@bendavies
• fix: Rename variable and fix variables descriptions (#75) @bendavies @leoblanc