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
Copy file name to clipboardExpand all lines: README.md
+28-9Lines changed: 28 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,16 +116,35 @@ By default the runner is registered on initial deployment. In previous versions
116
116
To register the runner automatically set the variable `gitlab_runner_registration_config["registration_token"]`. This token value can be found in your GitLab project, group, or global settings. For a generic runner you can find the token in the admin section. By default the runner will be locked to the target project, not run untagged. Below is an example of the configuration map.
117
117
118
118
```hcl
119
-
gitlab_runner_registration_config = {
120
-
registration_token = "<registration token>"
121
-
tag_list = "<your tags, comma separated>"
122
-
description = "<some description>"
123
-
locked_to_project = "true"
124
-
run_untagged = "false"
125
-
maximum_timeout = "3600"
126
-
access_level = "<not_protected OR ref_protected, ref_protected runner will only run on pipelines triggered on protected branches. Defaults to not_protected>"
access_level = "<not_protected OR ref_protected, ref_protected runner will only run on pipelines triggered on protected branches. Defaults to not_protected>"
130
+
}
127
131
}
128
-
```
132
+
133
+
# obtain this token from your Gitlab instance and store it manually in the SSM parameter
0 commit comments