You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: support per-runner-flavor SQS batch size and window in multi_runner_config
Add lambda_event_source_mapping_batch_size and
lambda_event_source_mapping_maximum_batching_window_in_seconds as
optional fields inside multi_runner_config.runner_config, falling back
to the existing module-level variables when not set via coalesce().
This follows the same pattern used by scale_up_reserved_concurrent_executions.
Agent-Logs-Url: https://github.com/github-aws-runners/terraform-aws-github-runner/sessions/1a1b641a-bbf5-45ab-bd97-73d9501552b9
Co-authored-by: Brend-Smits <15904543+Brend-Smits@users.noreply.github.com>
runners_maximum_count: "The maximum number of runners that will be created. Setting the variable to `-1` desiables the maximum check."
233
235
scale_down_schedule_expression: "Scheduler expression to check every x for scale down."
234
236
scale_up_reserved_concurrent_executions: "Amount of reserved concurrent executions for the scale-up lambda function. A value of 0 disables lambda from being triggered and -1 removes any concurrency limitations."
237
+
lambda_event_source_mapping_batch_size: "(Optional) Maximum number of records per Lambda invocation for this runner flavor. Overrides the module-level `lambda_event_source_mapping_batch_size` when set."
238
+
lambda_event_source_mapping_maximum_batching_window_in_seconds: "(Optional) Maximum seconds to gather records before invoking Lambda for this runner flavor. Overrides the module-level `lambda_event_source_mapping_maximum_batching_window_in_seconds` when set."
235
239
userdata_template: "Alternative user-data template, replacing the default template. By providing your own user_data you have to take care of installing all required software, including the action runner. Variables userdata_pre/post_install are ignored."
236
240
enable_jit_config "Overwrite the default behavior for JIT configuration. By default JIT configuration is enabled for ephemeral runners and disabled for non-ephemeral runners. In case of GHES check first if the JIT config API is available. In case you are upgrading from 3.x to 4.x you can set `enable_jit_config` to `false` to avoid a breaking change when having your own AMI."
237
241
enable_runner_detailed_monitoring: "Should detailed monitoring be enabled for the runner. Set this to true if you want to use detailed monitoring. See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html for details."
0 commit comments