af2a2d0f42
For providers which do not natively support secrets (which is all of them today), we annotate output values coming back from the provider if there is a coresponding secret input in the inputs we passed in. This logic was not tearing into rich objects, so if you passed a secret as a member of an array or object into a resource provider, we would lose the secretness on the way back. Because of the interaction with Check (where we call Check and then take the values returned by the provider as inputs for all calls to Diff/Update), this would apply not only to the Output values of a resource but also the Inputs (because the secret metadata would not flow from the inputs of check to the outputs). This change augments our logic which transfers secrets metadata from one property map to another to handle these additional cases. |
||
|---|---|---|
| .. | ||
| compat/v0.10.0/minimal | ||
| dynamic-provider | ||
| formattable | ||
| minimal | ||
| secrets | ||
| examples_test.go | ||