c1f7193454
Calling the nonsensitive function with values which are not sensitive will result in an error. This restriction was added with the goal of preventing confusingly redundant use of this function. Unfortunately, this breaks when using nonsensitive to reveal the value of sensitive resource attributes. This is because the validate walk does not (and cannot) mark attributes as sensitive based on the schema, because the resource value itself is unknown. This commit therefore alters this restriction such that it permits nonsensitive unknown values, and adds a test case to cover this specific scenario. |
||
|---|---|---|
| .. | ||
| blocktoattr | ||
| funcs | ||
| testdata/functions-test | ||
| data.go | ||
| data_test.go | ||
| doc.go | ||
| eval.go | ||
| eval_test.go | ||
| functions.go | ||
| functions_test.go | ||
| references.go | ||
| scope.go | ||