Skip to content

CI/CD variable values should be non-sensitive by default

Description

Removes the sensitive setting from instance/group/project level CI/CD variables. It should be at the discretion of Terraform and the infra developer to mark values as sensitive.

In a very big gitops project of us all sensitive values are still marked as sensitive in the state as they are either input variables set as sensitive or derived from sensitive values like the runner_token.

Closes: #758 (closed)

PR Checklist

  • (not applicable) Resource attributes match 1:1 the names and structure of the API resource in the GitLab API documentation.
  • (not applicable) Examples are updated with:
    • A *.tf file for the resource/s with at least one usage example
    • A *.sh file for the resource/s with an import example (if applicable)
  • Documentation re-generated.
  • (not applicable) New resources have at minimum a basic test with three steps:
    • Create the resource
    • Update the attributes
    • Import the resource
  • No new //lintignore comments that came from copied code. Linter rules are meant to be enforced on new code.
Edited by Timo Furrer

Merge request reports