Skip to content

fix: added sensitive flag to input variables #177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 15, 2025
Merged

fix: added sensitive flag to input variables #177

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions modules/eso-secretstore/variables.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,7 @@ variable "sstore_secret_apikey" {
description = "APIkey to be stored into var.sstore_secret_name secret to authenticate with Secrets Manager instance"
type = string
default = null
sensitive = true
validation {
condition = var.eso_authentication == "api_key" ? var.sstore_secret_apikey != null : true
error_message = "API Key authentication is enabled and scope for store is cluster, therefore sstore_secret_apikey must be provided."
Expand Down
1 change: 1 addition & 0 deletions solutions/fully-configurable/variables.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ variable "secrets_manager_ibmcloud_api_key" {
type = string
description = "API key to authenticate on Secrets Manager instance. If null the ibmcloud_api_key will be used."
default = null
sensitive = true
}

variable "provider_visibility" {
Expand Down