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
This fearure will be removed since we introducing the EventBridge. Same functinallity can be implemented by adding a rule to the EventBridge to forward `workflow_job` events to the SQS queue.
337
+
This feaTure will be removed since we introducing the EventBridge. Same functionality can be implemented by adding a rule to the EventBridge to forward `workflow_job` events to the SQS queue.
338
338
339
-
This queue is an experimental feature to allow you to receive a copy of the wokflow_jobs events sent by the GitHub App. This can be used to calculate a matrix or monitor the system.
339
+
Below an example how you can sent all `workflow_job` with action `in_progress`to a SQS queue.
340
340
341
-
To enable the feature set `enable_workflow_job_events_queue = true`. Be aware though, this feature is experimental!
341
+
```hcl
342
342
343
-
Messages received on the queue are using the same format as published by GitHub wrapped in a property `workflowJobEvent`.
This extensible format allows more fields to be added if needed.
352
-
You can configure the queue by setting properties to `workflow_job_events_queue_config`
363
+
353
364
354
365
NOTE: By default, a runner AMI update requires a re-apply of this terraform config (the runner AMI ID is looked up by a terraform data source). To avoid this, you can use `ami_id_ssm_parameter_name` to have the scale-up lambda dynamically lookup the runner AMI ID from an SSM parameter at instance launch time. Said SSM parameter is managed outside of this module (e.g. by a runner AMI build workflow).
0 commit comments