From 79831430938465a7fd868ddd7bce3a8e294f384f Mon Sep 17 00:00:00 2001 From: "forest-releaser[bot]" <80285352+forest-releaser[bot]@users.noreply.github.com> Date: Mon, 28 Oct 2024 17:59:44 +0100 Subject: [PATCH] chore(main): release 5.18.0 (#4207) :robot: I have created a release *beep* *boop* --- ## [5.18.0](https://github.com/philips-labs/terraform-aws-github-runner/compare/v5.17.3...v5.18.0) (2024-10-28) ### Features * support AWS EventBridge ([#4188](https://github.com/philips-labs/terraform-aws-github-runner/issues/4188)) ([9607ca6](https://github.com/philips-labs/terraform-aws-github-runner/commit/9607ca65a8b2c9a62936b28e823c6d7865d3ca38)) ### Migration directions This release is adding optional the [EventBridge](https://philips-labs.github.io/terraform-aws-github-runner/configuration/#eventbridge) as option to the webhook. No matter if the feature is enabled or not resources are moved internally. Which will destroy all webhook related resources update to this verions. To retain data for the Loggroup of the webhook or mmetrics for the webhook the resources not to be moved in the Terraform state. You can add HCL moved blocked to your deployment to instruct Terraform to move the resources instead of re-create.
Examples Terraform `moved` blockes #### With module defaults or eventbridge is not eanavbled ```hcl # log group moved { from = module..module.webhook.aws_cloudwatch_log_group.webhook to = module..module.webhook.module.direct[0].aws_cloudwatch_log_group.webhook } # lambda moved { from = module..module.webhook.aws_lambda_function.webhook to = module..module.webhook.module.direct[0].aws_lambda_function.webhook } ``` #### With EventBridge enabled ```hcl # log group moved { from = module..module.webhook.aws_cloudwatch_log_group.webhook to = module..module.webhook.module.direct[0].aws_cloudwatch_log_group.webhook } # lambda moved { from = module..module.webhook.aws_lambda_function.webhook to = module..module.webhook.module.direct[0].aws_lambda_function.webhook } ``` #### Ater upgrade swithcing between webhook to EventBridge When enable mode `eventbridge` ```hcl # log group moved { from = module.runners.module.webhook.module.direct[0].aws_cloudwatch_log_group.webhook to = module.runners.module.webhook.module.eventbridge[0].aws_cloudwatch_log_group.webhook } # lambda moved { from = module.runners.module.webhook.module.direct[0].aws_lambda_function.webhook to = module.runners.module.webhook.module.eventbridge[0].aws_lambda_function.webhook } ``` Or vice versa for moving from `eventbride` to `webhook`
--- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: forest-releaser[bot] <80285352+forest-releaser[bot]@users.noreply.github.com> --- CHANGELOG.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index a1ca2e1e74..22fea97d2e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,12 @@ # Changelog +## [5.18.0](https://github.com/philips-labs/terraform-aws-github-runner/compare/v5.17.3...v5.18.0) (2024-10-28) + + +### Features + +* support AWS EventBridge ([#4188](https://github.com/philips-labs/terraform-aws-github-runner/issues/4188)) ([9607ca6](https://github.com/philips-labs/terraform-aws-github-runner/commit/9607ca65a8b2c9a62936b28e823c6d7865d3ca38)) + ## [5.17.3](https://github.com/philips-labs/terraform-aws-github-runner/compare/v5.17.2...v5.17.3) (2024-10-23)