pulumi/sdk/nodejs/runtime
Matt Ellis 2ff54fa150 Push secretness "up" while deserializing objects.
Since we don't support nesting secrets (as they are modeled as
Outputs), as we deserialize, we push the secretness up to top level,
where we will correctly use it to mark the output as secret.

This fixes an issue where if you created a StackReference resource,
with a mix of secret and non secret properties, you would see the
"wire form" of the secrets as values on the `outputs` map of the
StackReference resource.
2019-05-10 17:07:52 -07:00
..
closure Work around a legal code pattern that previous versions of TypeScript complain about. (#2631) 2019-04-08 11:21:01 -07:00
config.ts Do not lazy initialize config or settings 2018-08-06 15:53:38 -07:00
debuggable.ts make the context-param non-optional for debuggable promises. (#2242) 2018-11-24 18:57:17 -08:00
index.ts Actually export type. (#1971) 2018-09-21 11:58:58 -07:00
invoke.ts Remove acceptsSecrets from InvokeRequest 2019-05-10 17:07:52 -07:00
resource.ts Rename SecretOutputs to AdditionalSecretOutputs 2019-05-10 17:07:52 -07:00
rpc.ts Push secretness "up" while deserializing objects. 2019-05-10 17:07:52 -07:00
settings.ts Do not flow secrets from NodeJS SDK to older CLIs 2019-05-10 17:07:52 -07:00
stack.ts Support Secret Outputs in the Node SDK 2019-05-10 17:07:52 -07:00