Replies: 1 comment 1 reply
-
The answer to this all depends on what version of Gitlab you are using and if you plan on ever updating. For future proofing I would suggest the authentication token. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm just getting started with the module so probably the next question is quite basic...
I see this in your documentation:
"The only parameter that needs to be provided is the name of a SSM parameter holding the Runner registration token and the URL of your GitLab instance". So I need to provide the runners REGISTRATION token. However, the gitlab documentation says:
"The ability to pass a runner registration token has been deprecated and is planned for removal in GitLab 18.0, along with support for certain configuration arguments. This change is a breaking change. GitLab has implemented a new GitLab Runner token architecture, which introduces a new method for registering runners and eliminates the runner registration token."
My question therefore is should I still use the Registration token option (although it is deprecated) or should I use the Authentication token (https://docs.gitlab.com/ee/security/tokens/index.html)?
Beta Was this translation helpful? Give feedback.
All reactions