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!: replace Amazon Linux 2 by Amazon Linux 2023 as default Linux AMI (#3437)
Replaces Amazon lLnux 2 (default) by Amazon Linux 2023. Impact for anyone relying on the default setup provided by the module.
---------
Co-authored-by: Niek Palm <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -528,7 +528,7 @@ We welcome any improvement to the standard module to make the default as secure
528
528
| <aname="input_instance_max_spot_price"></a> [instance\_max\_spot\_price](#input\_instance\_max\_spot\_price)| Max price price for spot instances per hour. This variable will be passed to the create fleet as max spot price for the fleet. |`string`|`null`| no |
529
529
| <aname="input_instance_profile_path"></a> [instance\_profile\_path](#input\_instance\_profile\_path)| The path that will be added to the instance\_profile, if not set the environment name will be used. |`string`|`null`| no |
530
530
| <aname="input_instance_target_capacity_type"></a> [instance\_target\_capacity\_type](#input\_instance\_target\_capacity\_type)| Default lifecycle used for runner instances, can be either `spot` or `on-demand`. |`string`|`"spot"`| no |
531
-
| <aname="input_instance_types"></a> [instance\_types](#input\_instance\_types)| List of instance types for the action runner. Defaults are based on runner\_os (amzn2 for linux and Windows Server Core for win). |`list(string)`| <pre>[<br> "m5.large",<br> "c5.large"<br>]</pre> | no |
531
+
| <aname="input_instance_types"></a> [instance\_types](#input\_instance\_types)| List of instance types for the action runner. Defaults are based on runner\_os (al2023 for linux and Windows Server Core for win). |`list(string)`| <pre>[<br> "m5.large",<br> "c5.large"<br>]</pre> | no |
532
532
| <aname="input_job_queue_retention_in_seconds"></a> [job\_queue\_retention\_in\_seconds](#input\_job\_queue\_retention\_in\_seconds)| The number of seconds the job is held in the queue before it is purged. |`number`|`86400`| no |
533
533
| <aname="input_key_name"></a> [key\_name](#input\_key\_name)| Key pair name |`string`|`null`| no |
534
534
| <aname="input_kms_key_arn"></a> [kms\_key\_arn](#input\_kms\_key\_arn)| Optional CMK Key ARN to be used for Parameter Store. This key must be in the current account. |`string`|`null`| no |
| <aname="input_ami_filter"></a> [ami\_filter](#input\_ami\_filter)| The amis to search. Use the default for the provided amazon linux image, `github-runner-windows-core-2019-*` for the provided Windows image |`string`|`github-runner-amzn2-x86_64-2021*`| no |
16
+
| <aname="input_ami_filter"></a> [ami\_filter](#input\_ami\_filter)| The amis to search. Use the default for the provided amazon linux image, `github-runner-windows-core-2019-*` for the provided Windows image |`string`|`github-runner-al2023-x86_64-2023*`| no |
17
17
| <aname="input_github_app_key_base64"></a> [github\_app\_key\_base64](#input\_github\_app\_key\_base64)| The base64 encoded private key you downloaded from GitHub when creating the app |`string`|| yes |
18
18
| <aname="input_github_app_id"></a> [github\_app\_id](#input\_github\_app\_id)| The id of the app you created on GitHub |`string`|| yes |
19
19
| <aname="input_region"></a> [region](#input\_region)| The target aws region |`string`|`eu-west-1`| no |
@@ -52,13 +52,13 @@ You will need to build your image. This example deployment uses the image exampl
52
52
53
53
To use your image in the terraform modules you will need to set some values on the module.
54
54
55
-
Assuming you have built the `linux-amzn2` image which has a pre-defined AMI name in the following format `github-runner-amzn2-x86_64-YYYYMMDDhhmm` you can use the following values.
55
+
Assuming you have built the `linux-al2023` image which has a pre-defined AMI name in the following format `github-runner-al2023-x86_64-YYYYMMDDhhmm` you can use the following values.
56
56
57
57
```hcl
58
58
module "runners" {
59
59
...
60
60
# set the name of the ami to use
61
-
ami_filter = { name = ["github-runner-amzn2-x86_64-2021*"], state = ["available"] }
61
+
ami_filter = { name = ["github-runner-al2023-x86_64-2023*"], state = ["available"] }
Copy file name to clipboardExpand all lines: images/README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,14 @@ The images inside this folder are pre-built images designed to shorten the boot
4
4
5
5
These images share the same scripting as used in the user-data mechanism in `/modules/runners/templates/`. We use a `templatefile` mechanism to insert the relevant script fragments into the scripts used for provisioning the images.
6
6
7
-
The examples in `linux-amzn2` and `windows-core-2019` also upload a `start-runner` script that uses the exact same startup process as used in the user-data mechanism. This means that the image created here does not need any extra scripts injected or changes to boot up and connect to GH.
7
+
The examples in `linux-al2023` and `windows-core-2019` also upload a `start-runner` script that uses the exact same startup process as used in the user-data mechanism. This means that the image created here does not need any extra scripts injected or changes to boot up and connect to GH.
8
8
9
9
## Building your own
10
10
11
11
To build these images you first need to install packer.
12
12
You will also need an amazon account and to have provisioned your credentials for packer to consume.
13
13
14
-
Assuming you are building the `linux-amzn2` image. Then run the following from within the `linux-amzn2` folder
14
+
Assuming you are building the `linux-al2023` image. Then run the following from within the `linux-al2023` folder
15
15
16
16
```bash
17
17
packer init .
@@ -25,12 +25,12 @@ Your image will then begin to build inside AWS and when finished you will be pro
25
25
26
26
To use your image in the terraform modules you will need to set some values on the module.
27
27
28
-
Assuming you have built the `linux-amzn2` image which has a pre-defined AMI name in the following format `github-runner-amzn2-x86_64-YYYYMMDDhhmm` you can use the following values.
28
+
Assuming you have built the `linux-al2023` image which has a pre-defined AMI name in the following format `github-runner-al2023-x86_64-YYYYMMDDhhmm` you can use the following values.
29
29
30
30
```hcl
31
31
# set the name of the ami to use
32
-
ami_filter = { name = ["github-runner-amzn2-x86_64-2021*"] }
33
-
# provide the owner id of
32
+
ami_filter = { name = ["github-runner-al2023-x86_64-2023*"] }
0 commit comments