pulumi/pkg/resource/plugin
Matt Ellis 294df77703 Retain secrets for unenlightented providers
When a provider does not natively understand secrets, we need to pass
inputs as raw values, as to not confuse it.

This leads to a not great experience by default, where we pass raw
values to `Check` and then use the results as the inputs to remaining
operations. This means that by default, we don't end up retaining
information about secrets in the checkpoint, since the call to `Check`
erases all of our information about secrets.

To provide a nicer experience we were don't lose information about
secrets even in cases where providers don't natively understand them,
we take property maps produced by the provider and mark any values in
them that are not listed as secret as secret if the coresponding input
was a secret.

This ensures that any secret property values in the inputs are
reflected back into the outputs, even for providers that don't
understand secrets natively.
2019-05-10 17:07:52 -07:00
..
analyzer.go Add license headers 2018-05-22 15:02:47 -07:00
analyzer_plugin.go Improve error message when failing to load plugins (#2542) 2019-03-11 22:17:01 +00:00
check.go Add license headers 2018-05-22 15:02:47 -07:00
config_source.go Add license headers 2018-05-22 15:02:47 -07:00
context.go Remove uses of plugins in the snapshot (#2662) 2019-04-23 09:53:44 -07:00
host.go Remove uses of plugins in the snapshot (#2662) 2019-04-23 09:53:44 -07:00
host_server.go Move management of root resource state to engine (#1944) 2018-09-18 11:47:34 -07:00
langruntime.go Add nodejs support for query mode 2019-05-02 18:08:08 -07:00
langruntime_plugin.go Add nodejs support for query mode 2019-05-02 18:08:08 -07:00
plugin.go Improve error message when failing to load plugins (#2542) 2019-03-11 22:17:01 +00:00
provider.go Refresh inputs (#2531) 2019-03-11 13:50:00 -07:00
provider_plugin.go Retain secrets for unenlightented providers 2019-05-10 17:07:52 -07:00
rpc.go Retain secrets for unenlightented providers 2019-05-10 17:07:52 -07:00
rpc_test.go Follow up on #2369 (#2397) 2019-01-28 17:38:16 -08:00