We'd like a method to be able to test if a secret is resolvable, as per this documentation here:

Harness supports expressions to check if a value is resolved instead of relying on null checks. The expression <+expression.isResolved(<+pipeline.variables.var1>)> verifies whether a variable resolves to a non-null value. Similarly, <+expression.isUnresolved(<+pipeline.variables.var1>)> can be used to check if a variable remains unresolved. It is recommended to use these expressions instead of <+<+pipeline.variables.var1> != null> for more reliable evaluation in pipelines.

The reason for this is to help our teams be able to prepare for cases where it isn't resolvable. We want to be able to use ternary situations to determine what should happen, and using the "is resolvable" doesn't seem to be able to check against the secret.