Runner
The gitlab.Runner resource allows to manage the lifecycle of a runner. A runner can either be registered at an instance level or group level. The runner will be registered at a group level if the token used is from a group, or at an instance level if the token used is for the instance. ~ Using this resource will register a runner using the deprecated registration_token flow. To use the new authentication_token flow instead, use the gitlab.UserRunner resource! Upstream API: GitLab REST API docs
Import
Starting in Terraform v1.5.0 you can use an import block to import gitlab_runner. For example: terraform import { to = gitlab_runner.example id = "see CLI command below for ID" } Import using the CLI is supported using the following syntax: A GitLab Runner can be imported using the runner's ID, eg
$ pulumi import gitlab:index/runner:Runner this 1Properties
The access_level of the runner. Valid values are: not_protected, ref_protected.
The authentication token used for building a config.toml file. This value is not present when imported.
The runner's description.
Free-form maintenance notes for the runner (1024 characters).
Maximum timeout set when this runner handles the job.
The registration token used to register the runner.
Whether the runner should handle untagged jobs.