pi-ux-ce@ARES c9ade2f851 In your try() block, when the attribute doesn't exist, it correctly returns . However, when the attribute does exist, it returns the whole nested object (e.g., { host = ..., name = ... }). In Terraform, comparing a complex object/map to an empty string ({...} != ) is technically invalid or doesn't evaluate cleanly to a false check, causing the filter to let it slip through or crash when it expects a string.

2026-10-13 18:47:57 +01:00

..

.tool-versions

cleanup

2026-10-13 16:15:59 +01:00

database.tf

module service

2026-10-13 17:53:30 +01:00

deployment.tf

module service

2026-10-13 17:42:09 +01:00

module.tf

enable multiple domain name

2026-10-13 18:04:22 +01:00

redis.tf

module service

2026-10-13 17:53:30 +01:00

secrets.tf

In your try() block, when the attribute doesn't exist, it correctly returns . However, when the attribute does exist, it returns the whole nested object (e.g., { host = ..., name = ... }). In Terraform, comparing a complex object/map to an empty string ({...} != ) is technically invalid or doesn't evaluate cleanly to a false check, causing the filter to let it slip through or crash when it expects a string.

2026-10-13 18:47:57 +01:00

storage.tf

reformat

2026-10-12 16:53:38 +01:00

variables.auto.tfvars

In your try() block, when the attribute doesn't exist, it correctly returns . However, when the attribute does exist, it returns the whole nested object (e.g., { host = ..., name = ... }). In Terraform, comparing a complex object/map to an empty string ({...} != ) is technically invalid or doesn't evaluate cleanly to a false check, causing the filter to let it slip through or crash when it expects a string.

2026-10-13 18:47:57 +01:00