mirror of https://github.com/pulumi/pulumi.git
020097d8d0
12072: sdk/node/StackReference: Add getOutputDetails r=abhinav a=abhinav NodeJS equivalent of the StackReference.GetOutputDetails method and accompanying type added to the Go SDK in #12034. This will allow users of the TypeScript and JavaScript SDKs to fetch outputs from stack references directly--without going through an Output type. Couple notes about testing: - `MockMonitor.readResource` kept exploding because the getCustom method was missing on the provided object. I didn't find any examples in the Node SDK of using mocks to test StackReferences, so I'm guessing this was an unexercised code path. I've fixed that. - It seems that the JavaScript SDK promotes an entire map to secret if an item inside it is a secret. So I had to isolate the two test cases into separate outputs to get the plain text case to be written as a "value". If there's a more correct way of setting up that mock, I'm happy to merge the outputs back into a single map for a more representative test case. Refs #10839, #5035 Co-authored-by: Abhinav Gupta <abhinav@pulumi.com> |
||
---|---|---|
.. | ||
automation | ||
mockpackage | ||
runtime | ||
sxs_ts_test | ||
config.spec.ts | ||
constants.ts | ||
init.spec.ts | ||
iterable.spec.ts | ||
options.spec.ts | ||
output.spec.ts | ||
provider.spec.ts | ||
resource.spec.ts | ||
stackReference.spec.ts | ||
unwrap.spec.ts | ||
util.ts |