Skip to content

Commit

Permalink
fix: delete the 'runner_config_toml_rendereded' output variable (#1019)
Browse files Browse the repository at this point in the history
## Description

Due to calls to `nonsensitive` in case the data is sensitive or not
calling the function in the other case, the code gets very complex. The
output variable `runner_config_toml_rendereded` was introduced for
easier debugging, but we still have the option to write the whole Runner
configuration to a local file (`debug.write_runner_config_to_file`).

This "fixers" that issue by just deleting the output variable.

Closes #1018

## Migrations required

Usually not. For debugging purposes, set the
`debug.write_runner_config_to_file` to `true`. The configuration is
written to a file on your local disk (directory `debug/`)

## Verification

Only linted as this is only deleting an output variable.
  • Loading branch information
JulianCBC committed Nov 10, 2023
1 parent d9e550e commit 3f7eaea
Showing 1 changed file with 0 additions and 5 deletions.
5 changes: 0 additions & 5 deletions outputs.tf
Original file line number Diff line number Diff line change
Expand Up @@ -57,8 +57,3 @@ output "runner_user_data" {
description = "(Deprecated) The user data of the Gitlab Runner Agent's launch template. Set `var.debug.output_runner_user_data_to_file` to true to write `user_data.sh`."
value = nonsensitive(local.template_user_data)
}

output "runner_config_toml_rendered" {
description = "The rendered config.toml given to the Runner Manager."
value = local.template_runner_config
}

0 comments on commit 3f7eaea

Please sign in to comment.